db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DERBY-3398) Support min/max values for Java types float/double in real/double columns
Date Sat, 16 Feb 2013 04:19:33 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579703#comment-13579703
] 

Dag H. Wanvik edited comment on DERBY-3398 at 2/16/13 4:19 AM:
---------------------------------------------------------------

Thanks, Knut. As for SQLDataException, now I have run this once and I'm satisfied the right
exception subclass is used, I guess we can move it back to SQLException; we have other tests
that check the subclasses (TestJDBC40EException).

I used some other constants to test that we accept smaller values than DB2_SMALLEST_POSITIVE_REAL
& friends. For example in table beyondDB2Real I used the constant "+1.174E-37f", smaller
than  DB2_SMALLEST_POSITIVE_REAL (+1.175E-37f), but we can add Float.MIN_NORMAL (1.17549435E-38)
too, sure.

I wasn't aware of the class loader issues you mention, I'll fix that.
                
      was (Author: dagw):
    Thanks, Knut. As for SQLDataException, now I have run this once and I'm satisfied the
right exception subclass is used, I guess we can move it back to SQLException; we have other
tests that check the subclasses (TestJDBC40EException).

I used some other constants to test that we accept smaller values than DB2_SMALLEST_POSITIVE_REAL
& friends. For example in table beyondDB2Real I used the constant "+1.174E-37f", smaller
than  DB2_SMALLEST_POSITIVE_REAL (+1.175E-37f) and also smaller than  Float.MIN_NORMAL, but
we can add Float.MIN_NORMAL (1.17549435E-38) too, sure. (The one I used is too small to be
normalized).

I wasn't aware of the class loader issues you mention, I'll fix that.
                  
> 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
>            Assignee: Dag H. Wanvik
>            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-5.diff, derby-3398-5.stat, 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

Mime
View raw message