[ 
https://issues.apache.org/jira/browse/DERBY-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim Haase updated DERBY-6083:
-----------------------------

    Attachment: DERBY-6083.zip
                DERBY-6083.stat
                DERBY-6083.diff

Attaching DERBY-6083.diff, DERBY-6083.stat, and DERBY-6083.zip, with changes as 
follows:

M       src/ref/rrefsqlj14122.dita
M       src/ref/rrefsqljdoubleprecision.dita
M       src/ref/rrefnumericlimits.dita

I redefined "smallest" and "largest" in addition to providing the new values. I 
also changed the sentence after each list in the data type topics.

Please let me know what changes are needed. I was also wondering about the 
topic on the FLOAT data type -- I am guessing the precisions are the same so no 
changes are needed here?

Thanks very much.
                
> 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

Reply via email to