Re: [SQLObject] Oracle support: sharing, unsized StringCols

[Andy T. <an...@gm...>]

On 11/11/05, Kevin Dangoor <da...@gm...> wrote:
> On 11/10/05, Dmitry Cheryasov <dch...@ot...> wrote:
> > Does anyone have an idea on how to handle StringCols that don't have
> > length set? Oracle does not have a notion of 'TEXT' type. Making such
> > columns varchar2(4000) would certainly be overkill. Making them CLOBs,
> > even more so. Raising an exception would probably be too rude :) Now I
> > resort to varchar2(4000) and a warning.
>
> Overkill as it may seem, I think CLOB is actually the intention there.
> If you specify a length, you want a varchar. But, without a length,
> you essentially want unbounded space. (Consider, for example, a CMS...
> it's very easy to make a page that is greater than 4K!)
>
> Kevin
>
>

I'm with Kevin here. Oracle's equivalent of MySQL's text datatype is
actually a CLOB.

They are just a bugger to use in PL/SQL which is why most large text
columns in Oracle databases get set to VARCHAR2(4000).

Regards,
Andy
--
From the desk of Andrew J Todd esq