db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Bouschen <mbo.t...@spree.de>
Subject Re: [jira] Commented: (JDO-206) JDOQL test NotEquals comparing floating point numbers
Date Sun, 18 Dec 2005 23:06:56 GMT
Hi Craig,

we could go through the schema and change the column type as you 
described, but maybe we should treat this as a separate issue. I still 
would like to change the float value and add the setUp changes as 
implemented in the patch. What do you think?

Regards Michael

>    [ http://issues.apache.org/jira/browse/JDO-206?page=comments#action_12360759 ] 
>Craig Russell commented on JDO-206:
>The issue here is that Derby treats the FLOAT data type is used to represent both single-
and double-precision floating point numbers. To get a single-precision value in the database,
you have to use either REAL data type or specify a length on FLOAT. 
>Everywhere we really want a 32-bit floating point number to be stored, we need to specify
REAL or FLOAT(24) as the column type.
>>JDOQL test NotEquals comparing floating point numbers
>>         Key: JDO-206
>>         URL: http://issues.apache.org/jira/browse/JDO-206
>>     Project: JDO
>>        Type: Bug
>>  Components: tck20
>>    Reporter: Andy Jefferson
>>    Assignee: Michael Bouschen
>> Attachments: JDO-206.patch
>>The current TCK test (carried over from JDO 1.0) for NotEquals, uses != operator on
floating point numbers. This is not a good practice, and is unreliable. Its probably the case
that the Equals test uses == on the same content, which also is not a good idea (as noted
in the latest spec). These tests need reviewing and a reliable alternate strategy adopting

Michael Bouschen		Tech@Spree Engineering GmbH
mailto:mbo.tech@spree.de	http://www.tech.spree.de/
Tel.:++49/30/235 520-33		Buelowstr. 66			
Fax.:++49/30/2175 2012		D-10783 Berlin			

View raw message