JDBC Floating point loss of precision
From: <dgwhitt_at_my-dejanews.com>
Date: Fri, 07 May 1999 14:54:17 GMT
Message-ID: <7guuql$aki$1_at_nnrp1.deja.com>
Does anyone know of problems accessing data types defined as NUMBER (without precision or scale) or FLOAT using the Oracle JDBC Thin client? We are experience this loss and don't if there is a problem in what we are doing or it is just not doable.
Date: Fri, 07 May 1999 14:54:17 GMT
Message-ID: <7guuql$aki$1_at_nnrp1.deja.com>
Does anyone know of problems accessing data types defined as NUMBER (without precision or scale) or FLOAT using the Oracle JDBC Thin client? We are experience this loss and don't if there is a problem in what we are doing or it is just not doable.
I can define three fields as:
NUMBER
FLOAT
NUMBER(10,10)
...put the same data in all three (0.00519) and for the first two fields I
retrieved a value of zero but on the third, I receive the actual value stored
in the table. The same code has been switched to use ODBC and all of the data
is retrieved correctly, as it is in SQL*PLUS and TOAD. Any suggestions are
greatly appreciated, Dianna Whitt
-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Fri May 07 1999 - 16:54:17 CEST