Re: Re[2]: TEXT vs VARCHAR

There is another issue with TEXT vs VARCHAR. A TEXT field is not handled well
by ODBC and MS Access. If there is an index on the TEXT field, the ODBC link
will fail, saying something like "Can Not Index a OLE field." OLE fields are Access's
attempt at a BLOB field, and they are not indexable.

If you are using ODBC, I would not use a TEXT field until you test it in your enviroment.

Have Fun,
Dave Huttleston Jr

On Tue, 10 Oct 2000 17:50:25 -0400, you wrote:
> Jean-Christophe Boggio <cat(at)thefreecat(dot)org> writes:
> >>> is there a limit on the upper limit of a VARCHAR? i cannot find one in the
> >>> documentation.
>
> TL> The physical limit is circa 1Gb under TOAST.
>
> > Excuse me, what is the 8kb-per-record size limit if we can have so
> > big fields ?
>
> Sorry --- TOAST is 7.1. In existing releases, TEXT, VARCHAR, and CHAR
> are all constrained by the BLCKSZ limit on total row size. But still,
> that offers no reason for choosing TEXT over VARCHAR or vice versa.
>
> regards, tom lane
>
>