Re: Oracle CLOB
From: The Magnet <art_at_unsu.com>
Date: Wed, 22 Sep 2010 20:45:58 -0700 (PDT)
Message-ID: <30ae6fc4-0ce3-48de-bf59-8df4343f46d8_at_g21g2000prn.googlegroups.com>
On Sep 22, 3:57�pm, "Gerard H. Pille" <g..._at_skynet.be> wrote:
> The Magnet wrote:
> > On Sep 22, 1:29 pm, "Gerard H. Pille"<g..._at_skynet.be> �wrote:
> >> The Magnet wrote:
> >>> On Sep 21, 12:22 pm, "Gerard H. Pille"<g..._at_skynet.be> � �wrote:
> >>>> The Magnet wrote:
> >>>>> Ok, this is probably simple, what I'm lost. �FYI: �We're on 10gR2.
>
> >>>>> I'm trying to update a CLOB column. �The procedure is being called
> >>>>> from PHP. �If the INSERT procedure is called then the object gets
> >>>>> inserted into the table properly:
>
> >>>> How does PHP connect to the database? � OCI8?
>
> >>> Yes, it uses OCI8. �I'm thinking there is a limitation somewhere
> >>> there, but I do not know enough about that. �Are you familiar with
> >>> OCI8?
>
> >> Yes, but I remember trying to store pictures in the database, without succes.
>
> >> In the example here (http://wiki.oracle.com/page/PHP+Oracle+FAQ), the blob is loaded from a file.
>
> >> Don't forget the limits of pure SQL. � Maybe you can only update when p_body< �4k.
>
> >> But you provide only enough information for guess-work. �There's quite a number of places where
> >> things can go wrong.
>
> > That is so strange. �Here is the procedure declaration:
>
> > PROCEDURE update_message_by_message_id (
> > � �p_message_id � � � NUMBER,
> > � �p_sec_id � � � � � NUMBER,
> > � �p_variables � � � �VARCHAR2,
> > � �p_name � � � � � � VARCHAR2,
> > � �p_body � � � � � � CLOB,
> > � �p_changed_by � � � VARCHAR2,
> > � �p_status � � � � � VARCHAR2) IS
>
> > Thoughts?
>
> The same as before: the update statement can only handle 4K.
>
> Have a look at the manuals on how to use dbms_lob package inside your procedure.
Date: Wed, 22 Sep 2010 20:45:58 -0700 (PDT)
Message-ID: <30ae6fc4-0ce3-48de-bf59-8df4343f46d8_at_g21g2000prn.googlegroups.com>
On Sep 22, 3:57�pm, "Gerard H. Pille" <g..._at_skynet.be> wrote:
> The Magnet wrote:
> > On Sep 22, 1:29 pm, "Gerard H. Pille"<g..._at_skynet.be> �wrote:
> >> The Magnet wrote:
> >>> On Sep 21, 12:22 pm, "Gerard H. Pille"<g..._at_skynet.be> � �wrote:
> >>>> The Magnet wrote:
> >>>>> Ok, this is probably simple, what I'm lost. �FYI: �We're on 10gR2.
>
> >>>>> I'm trying to update a CLOB column. �The procedure is being called
> >>>>> from PHP. �If the INSERT procedure is called then the object gets
> >>>>> inserted into the table properly:
>
> >>>> How does PHP connect to the database? � OCI8?
>
> >>> Yes, it uses OCI8. �I'm thinking there is a limitation somewhere
> >>> there, but I do not know enough about that. �Are you familiar with
> >>> OCI8?
>
> >> Yes, but I remember trying to store pictures in the database, without succes.
>
> >> In the example here (http://wiki.oracle.com/page/PHP+Oracle+FAQ), the blob is loaded from a file.
>
> >> Don't forget the limits of pure SQL. � Maybe you can only update when p_body< �4k.
>
> >> But you provide only enough information for guess-work. �There's quite a number of places where
> >> things can go wrong.
>
> > That is so strange. �Here is the procedure declaration:
>
> > PROCEDURE update_message_by_message_id (
> > � �p_message_id � � � NUMBER,
> > � �p_sec_id � � � � � NUMBER,
> > � �p_variables � � � �VARCHAR2,
> > � �p_name � � � � � � VARCHAR2,
> > � �p_body � � � � � � CLOB,
> > � �p_changed_by � � � VARCHAR2,
> > � �p_status � � � � � VARCHAR2) IS
>
> > Thoughts?
>
> The same as before: the update statement can only handle 4K.
>
> Have a look at the manuals on how to use dbms_lob package inside your procedure.
Well, sorry for being like this. But a CLOB can handle 4GB, right? So, I would think the problem is between PHP and Oracle, maybe something in the communication? Received on Wed Sep 22 2010 - 22:45:58 CDT