Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <777601653.1113501437613.JavaMail.jira@ajax.apache.org>
Date: Thu, 14 Apr 2005 19:57:17 +0200 (CEST)
From: "Myrna van Lunteren (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-225) insert of decimal value larger than max
 succeeds with jdk15
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

insert of decimal value larger than max succeeds with jdk15
-----------------------------------------------------------

         Key: DERBY-225
         URL: http://issues.apache.org/jira/browse/DERBY-225
     Project: Derby
        Type: Bug
  Components: JDBC  
    Versions: 10.0.2.1    
    Reporter: Myrna van Lunteren
     Fix For: 10.0.2.2


On the following table:
   create table tmp (d decimal(31,0));
an insert of a value with a precision larger than 31:
   insert into tmp values (+1.79769E+308);
Should fail with:
   ERROR 22003: The resulting value is outside the range for the data type DECIMAL/NUMERIC(31,0).

However, with jdk15, it does not.

The expected error is generated from org.apache.derby.iapi.types.SQLDecimal.setWidth(), which calls getWholeDigits(), which gets the length of a string based on a BigDecimal using toString, which has a different value using jdk14 vs. jdk15 since the fix for DERBY-38.

Note: I verified that the fix for DERBY-38 did not per se cause this failure.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira