[
https://issues.apache.org/jira/browse/DERBY-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553410
]
Thomas Nielsen commented on DERBY-3290:
---------------------------------------
Yes, it is definately more complex and involved than just removing the checks
in NumberDataType.normalizeDOUBLE(). That is simply the codeline where Derby
enforces this.
All of these considerations/questions, and possibly more, may be (one of) the
reason(s) behind the SQL standard not touching on this at all but limits SQLs
scope to approximate numeric.
> Derby cannot store java Double or Float values .NaN and
> .[POSITIVE|NEGATIVE]_INFINITY
> -------------------------------------------------------------------------------------
>
> Key: DERBY-3290
> URL: https://issues.apache.org/jira/browse/DERBY-3290
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Reporter: Thomas Nielsen
> Priority: Minor
> Attachments: TestNaN.java
>
>
> Issue originally reported on derby-user, where user cannot store .NaN or
> .INFINITE for java datatypes Double or Float.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
