Re: ResultSet getString() result differs in 8.3 jdbc (compared to 8.1), with "real" type

Поиск
Список
Период
Сортировка
От Kris Jurka
Тема Re: ResultSet getString() result differs in 8.3 jdbc (compared to 8.1), with "real" type
Дата
Msg-id Pine.BSO.4.64.0905141441030.12930@leary.csoft.net
обсуждение исходный текст
Ответ на ResultSet getString() result differs in 8.3 jdbc (compared to 8.1), with "real" type  (Tanel <tanel.ehrenpreis@finestmedia.ee>)
Ответы Re: ResultSet getString() result differs in 8.3 jdbc (compared to 8.1), with "real" type
Список pgsql-jdbc

On Thu, 14 May 2009, Tanel wrote:

> I made some searches also, however found nothing exactly related to this
> problem. We just shifted from using 8.1 driver to 8.3 however seems that 8.3
> driver handles differently Postgresql floating type values, when using
> org.postgresql.jdbc2.AbstractJdbc2ResultSet.java getString() on them ?
> For example, when there is "real" type value 20.7 in database and we try to
> get it through getString() then old 8.1 driver returns nicely 20.7, but new
> 8.3 driver is returning something like 20.700001.
>
> So my question would be that if such getString() behaviour is desired (?)
> (it is also in 8.4 driver), then can someone please give an hint where
> exactly can this behaviour be manipulated/turned off/etc... ?
>

The setting that changed is extra_float_digits.  The newer driver is
setting it to two rather than the default zero to restore float values as
accurately as possible.  You can override this by issuing your own SET
command upon connection.

http://www.postgresql.org/docs/8.3/static/runtime-config-client.html#RUNTIME-CONFIG-CLIENT-FORMAT

Kris Jurka

В списке pgsql-jdbc по дате отправления:

Предыдущее
От: Kris Jurka
Дата:
Сообщение: Re: prepared statement not working
Следующее
От: Kris Jurka
Дата:
Сообщение: Re: v604 in Maven