db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@apache.org>
Subject Re: Double.NaN in table?
Date Wed, 19 Dec 2007 16:30:37 GMT
Andrew ``Bass'' Shcheglov wrote:
> On Dec 19, 2007 12:23 PM, Thomas Nielsen <Thomas.Nielsen@sun.com> wrote:
>> Looking at the derby code on the main trunk, I see the exception is
>> intentional, as there is an explicit check for NaN values in
>> NumberDataType.normalizeDOUBLE().
>>
>> Not sure if this is another DB2 compatability issue/limitation or not.
>> Maybe someone with deeper knowledge can give more details on this?
> 
> 
> This is odd,
> 
> for Oracle, for instance, fully supports IEEE 754 (since 10g):
> 
> http://www.oracle.com/technology/sample_code/tutorials/jdbc10g/ieeedatatypes/files/IEEEDatatypes.pdf

Note that's Oracle specific and non-standard, requires:

   - a Oracle specific SQL data type BINARY_DOUBLE or BINARY_FLOAT
   - requires use of the Oracle specific 
setBinaryDouble()/setBinaryFloat() after casting the PreparedStatement 
down to an OraclePreparedStatement.

Dan.



Mime
View raw message