Re: TEXT columns should indentify as java.sql.Types.CLOB
От | Kevin Grittner |
---|---|
Тема | Re: TEXT columns should indentify as java.sql.Types.CLOB |
Дата | |
Msg-id | 4C6904C00200002500034672@gw.wicourts.gov обсуждение исходный текст |
Ответ на | Re: TEXT columns should indentify as java.sql.Types.CLOB (Thomas Kellerer <spam_eater@gmx.net>) |
Ответы |
Re: TEXT columns should indentify as java.sql.Types.CLOB
|
Список | pgsql-jdbc |
Thomas Kellerer <spam_eater@gmx.net> wrote: > Oliver Jowett wrote on 16.08.2010 13:18: >> Returning Types.CLOB would imply that the preferred way to deal >> with those columns is via getClob() / setClob(), which surely >> isn't correct for TEXT columns in most cases? >> > > Not necessarily. > > Almost all drivers I know (Oracle, jTDS, MySQL and DB2 I think) > can handle getString() on a CLOB column without problems. (Oracle > only since it's 10.x drivers) I'm with Oliver. I've developed a lot of highly portable code, and *my* assumption would be that a column categorized as Types.CLOB would support getClob() / setClob(). That it might or might not support getString() seems pretty irrelevant to the issue. Your argument seems to be that if something behaves like character varying without the length limitations of some other database products on such types, it should be considered CLOB. I think it should be related to whether the CLOB access methods are supported. -Kevin
В списке pgsql-jdbc по дате отправления: