Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 15 Feb 2013 07:29:12 +0000 (UTC)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12388178.1202468708505.292172.1360913352980@arcas>
In-Reply-To: <JIRA.12388178.1202468708505@arcas>
References: <JIRA.12388178.1202468708505@arcas>
Subject: [jira] [Updated] (DERBY-3398) Support min/max values for Java types
 float/double in real/double columns
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dag H. Wanvik updated DERBY-3398:
---------------------------------

    Attachment: derby-3398-5.stat
                derby-3398-5.diff

Uploading patch #5, which implements the deferred check on DB2 limits in soft upgrade mode, when no lcc is present, cf. discussion above.

The upgrade tests now verify this distinction, cf. the "defer" parameter to Changes10_10#verifyDB2Behavior.

The patch also adds upgrade tests for the ResultSet#updateXXX case.

 Rerunning regressions.
                
> 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-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