db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
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
Date Sat, 30 Apr 2005 04:58:43 GMT
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



Mime
View raw message