[
https://issues.apache.org/jira/browse/DERBY-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553366
]
Thomas Nielsen commented on DERBY-3290:
---------------------------------------
Let's not get too philosophical - NaN is still a legal value for the numeric
data type used in the java application, and users may want to store that for
whatever reason(s) they have. As of today they have to work around this by
adding extra columns (or otherwise) to flag NaN and/or infinite values.
Like you say Chapter 4.4.2 of [3] does indeed limit what is allowed as a REAL,
FLOAT and DOUBLE PRECISION value, and could also be the reason for the lack of
support in many (most?) databases for NaN and infinity numbers.
Proper support for IEEE 754 floating point numbers (even if it's borderline
with the SQL spec) would still be very welcome to a lot of
university/scientifc derby users IMHO.
> 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.
