Hi,
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.
As "real" is floating type value then presumably this long 20.700001 can
indeed be how database is holding value 20.7 ? However when I was comparing
8.1 and 8.3 driver sources then no changes that could have caused it caught
my eye...
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... ?
(NB! yes, the correct way would be to use getFloat() ofcourse)
Regards,
Tanel.
--
View this message in context:
http://www.nabble.com/ResultSet-getString%28%29-result-differs-in-8.3-jdbc-%28compared-to-8.1%29%2C-with-%22real%22-type-tp23536933p23536933.html
Sent from the PostgreSQL - jdbc mailing list archive at Nabble.com.