[
https://issues.apache.org/jira/browse/DERBY-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578936#comment-13578936
]
Dag H. Wanvik commented on DERBY-3398:
--------------------------------------
Thanks, guys. What you suggest could be a way forward here. The only downside I
see is that applications in soft upgrade mode relying on the DB limits checks
would see a deferred checking on embedded in the lcc-less scenarios, whereas
before soft upgrade they got an immediate check.
I think we could accept that small behavior change and handle it with a release
note. Does anybody think this is (too) risky?
> Support min/max values for Java types float/double in real/double columns
> -------------------------------------------------------------------------
>
> Key: DERBY-3398
> URL: https://issues.apache.org/jira/browse/DERBY-3398
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.4.1.3
> Reporter: Knut Anders Hatlen
> Priority: Minor
> Labels: derby_triage10_10
> Attachments: derby-3398-2.diff, derby-3398-3.diff, derby-3398-3.stat,
> derby-3398-4.diff, derby-3398.diff, derby-3398.status
>
>
> Derby doesn't support the entire range of valid (finite) values of the Java
> primitive types double/float in columns with SQL type DOUBLE or REAL. This
> appears to be a limitation that was introduced for compatibility with DB2.
> There have been some requests on derby-user that we lift this restriction.
> The restriction is enforced by the methods normalizeREAL() and
> normalizeDOUBLE() in org.apache.derby.iapi.types.NumberDataType.
--
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
