Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <42731083.5080309@sbcglobal.net>
Date: Fri, 29 Apr 2005 21:58:43 -0700
From: Kathey Marsden <kmarsdenderby@sbcglobal.net>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: [PATCH]  Derby-250 With client setObject( parameterIndex, x,
 java.sql.DOUBLE) throws conversion exception if the object passed is a
 BigDecimal
 with more than 31 digits
References: <42722F24.9050706@sbcglobal.net> <42726B4C.2080306@Sourcery.Org>
 <427278D5.6010007@debrunners.com>
In-Reply-To: <427278D5.6010007@debrunners.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Daniel John Debrunner wrote:

>So what happens if the value passed has more than 31 digits?
>Does the placement of the decimal point affect the behaviour?
>
>E.g. what's the outcome for these values?
>
>12345678901234567890123456789012
>
>1.2345678901234567890123456789012
>
>
>  
>
I have a feeling I might not quite be getting your question but will
take a stab at it.
They get converted on the client and will  insert into the double column
but lose precision as they do with embedded..
For these inserted values:

    new  BigDecimal("12345678901234567890123456789012")  -->
1.2345678901234567E31
     new BigDecimal("1.2345678901234567890123456789012")
-->1.2345678901234567


There is still an issue with setBigDecimal which will still throw an
exception with these values with the client.  A solution to that one is
not as clear to me, but I will file a bug for it.

Thanks

Kathey