LONG vs CLOB (Was: LONG fields within triggers.)

Thanks again Jack.

> It would be better in the long run (maybe even the long raw
> run!) if you used a BLOB. That way the features of the
> DBMS_LOB package would be available to you, not to mention
> out-of-line storage options galore.

I'm aware that LONG eventually will be discontinued - anyone know when? We mainly use the large data types for streaming data, eg. pictures - so far we've not been able to get the same throughput (bytes/sec) from (even optimized) LOB fields.

In this specific case, I'm indexing text, at most 100k/record I reckon and the CLOB overhead would probably be negligible - I probably spent more time on making the triggers than the entire accumulated overhead will be for the next decade! But the learning experience was great :)

Morten

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Morten Primdahl
  INET: morten_at_caput.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).