db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-5534) ResultSet#updateFloat, #updateDouble do not check for NaN on client
Date Tue, 13 Dec 2011 01:49:30 GMT
ResultSet#updateFloat, #updateDouble do not check for NaN on client
-------------------------------------------------------------------

                 Key: DERBY-5534
                 URL: https://issues.apache.org/jira/browse/DERBY-5534
             Project: Derby
          Issue Type: Bug
          Components: JDBC, Network Client
            Reporter: Dag H. Wanvik
            Priority: Minor


Embedded throws out of range when the argument is Float.Nan or Double.NaN, the client does
not catch it in updateXXX, where XXX is one of Float or Double,
The server will balk when the row is updated, though. (ResultSet#updateRow)
It will more regular if this is caught in updateXXX as other range errors are.
The SQL state is 22003, which is what embedded throws on updateXXX. See also DERBY-5533.




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message