Re: Bug in 7.4_213 driver: returns VARCHAR instead of

[Barry Lind <blind(at)xythos(dot)com>]

Kris Jurka wrote:
> I'm not so sure anymore.  While text can be used for storing large values
> it often isn't.  Further returning LONGVARCHAR could be a sign for the
> caller to use something like ResultSet.getCharacterStream instead of a
> simple getString.

I would agree.  In our applications we exclusively use text everywhere 
we use varchar on other databases.  I am quite sure that a change like 
this would break peoples existing apps.  I also agree that LONGVARCHAR 
would imply that you should use the getXXXStream methods which I would 
say is rarely the correct thing to do.  In my opinion text is just a 
better version of varchar (without many of the limitations imposed on 
varchar in other database vendor implementations).

--Barry