db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-206) JDOQL test NotEquals comparing floating point numbers
Date Sun, 18 Dec 2005 21:44:35 GMT
    [ 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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message