Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD4B1EF9D for ; Wed, 20 Feb 2013 14:11:18 +0000 (UTC) Received: (qmail 88579 invoked by uid 500); 20 Feb 2013 14:11:18 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 88273 invoked by uid 500); 20 Feb 2013 14:11:14 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 87925 invoked by uid 99); 20 Feb 2013 14:11:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2013 14:11:13 +0000 Date: Wed, 20 Feb 2013 14:11:13 +0000 (UTC) From: "Kim Haase (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582197#comment-13582197 ] Kim Haase commented on DERBY-3398: ---------------------------------- Just checking -- does this fix have any documentation impact, or should we leave the described limits as they are in http://db.apache.org/derby/docs/10.9/ref/rrefnumericlimits.html, http://db.apache.org/derby/docs/10.9/ref/rrefsqljdoubleprecision.html, and http://db.apache.org/derby/docs/10.9/ref/rrefsqlj14122.html? > 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 > Fix For: 10.10.0.0 > > 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-7.diff, derby-3398-7.stat, derby-3398-8.diff, derby-3398.diff, derby-3398.status, releaseNote.html, releaseNote.html > > > 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