[
https://issues.apache.org/jira/browse/DERBY-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583860#comment-13583860
]
Dag H. Wanvik commented on DERBY-6083:
--------------------------------------
One item: I am not sure if this has been discussed in out docs anywhere: Derby
normalizes -0.0 to positive 0.0.
Although it can be deduced from what we say, it may be helpful to point out
that we throw an exception if we calculate or try to store NaN or +/-
inifinity too (as defined by IEEE 754 and represented with named constants in
Java, e.g. Double.NaN).
> Update minimum/maximum floating-point values to align with DERBY-3398 fixes
> ---------------------------------------------------------------------------
>
> Key: DERBY-6083
> URL: https://issues.apache.org/jira/browse/DERBY-6083
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Affects Versions: 10.10.0.0
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-6083.diff, DERBY-6083.stat, DERBY-6083.zip
>
>
> The limits for floating-point values have changed as a result of DERBY-3398
> and should be documented:
> Smallest DOUBLE: 4.9e-324 (aka Double.MIN_VALUE)
> Largest DOUBLE: 1.7976931348623157e+308 (aka Double.MAX_VALUE)
> Smallest positive DOUBLE: 2.2250738585072014E-308 (aka Double.MIN_NORMAL)
> Largest negative DOUBLE: -2.2250738585072014E-308
> Smallest REAL: 1.4e-45 (aka Float.MIN_VALUE)
> Largest REAL: 3.4028235e+38 (aka Float.MAX_VALUE)
> Smallest positive REAL: 1.17549435E-38 (aka Float.MIN_NORMAL)
> Largest negative REAL: -1.17549435E-38
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
