Re: Oracle CLOB

> On Sep 23, 11:36 am, "Gerard H. Pille" <g..._at_skynet.be> wrote:
>> The Magnet wrote:
>>
>> > 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?
>>
>> Read my lips: Oracle SQL can only handle 4K.
>
>
> 4k? What is the use of CLOB if it can only handle 4k, make it a
> VARCHAR2? That makes no sense.
>
> A stored procedure should be able to receive a CLOB and store it in a
> CLOB column. Heck, think of the articles on CNN and other sites. Do
> you think they are only 4k? Most images are greater than 4k also.
>

Ask yourself this simple question.

If all clob processing could be handled by simple SQL from within PL/SQL, why would they provide a special pl/sql package for manipulating blobs/clobs?

Highly recommend you read the developers guide section on working with large objects. In particular, note the sections about the differences between clob locators and data, the impact of opening and closing clob locators, the importance of locking rows that need to e updated i.e. select for update etc.

Tim

-- 
tcross (at) rapttech dot com dot au