[
https://issues.apache.org/jira/browse/DERBY-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583876#comment-13583876
]
Kim Haase commented on DERBY-6083:
----------------------------------
Thanks, Dag! I suppose the NaN/infinity/zero info should be added to both the
REAL and DOUBLE PRECISION topics. I will fix the inconsistent "e"s too.
Do we really normalize -0 to +0? See, for example,
http://db.apache.org/derby/docs/10.9/ref/rreffuncasin.html.
I have not actually looked beyond the obvious places for mentions of the f-p
values but I probably should do some grepping just to be sure.
> 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
