db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayaram Subramanian (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5534) ResultSet#updateFloat, #updateDouble do not check for NaN and other conditions on client
Date Sun, 20 May 2012 04:38:40 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279660#comment-13279660

Jayaram Subramanian commented on DERBY-5534:

Curious in taking up this task. I also noted in comment that to reproduce this behavior, parametermappingtest
need to be enabled for client. How can this be done?.
> ResultSet#updateFloat, #updateDouble do not check for NaN and other conditions on client
> ----------------------------------------------------------------------------------------
>                 Key: DERBY-5534
>                 URL: https://issues.apache.org/jira/browse/DERBY-5534
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions:
>            Reporter: Dag H. Wanvik
>            Priority: Minor
>              Labels: derby_triage10_9
> In updateXXX, where XXX is one of Float or Double, embedded throws value out of range
when the argument is Float.NaN or Double.NaN, the client does not catch it.
> The server will balk when the row is updated, though, in ResultSet#updateRow. It will
be more regular if this is caught in updateXXX also on the client as other range errors are.
 The SQL state seen 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


View raw message