[
https://issues.apache.org/jira/browse/DERBY-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171066#comment-13171066
]
Dag H. Wanvik commented on DERBY-5534:
--------------------------------------
Even if DERBY-3398 were lifted, the client needs to check underflow, e.g. when
trying to do updateDouble(Double.MIN_VALUE) on a REAL column. The server does
check this, cf. SQLReal#setValue(double): it check against 0.0 before and after
narrowing double to float.
> 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
>
> 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
