db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
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 Fri, 29 Apr 2005 18:11:33 GMT

> Kathey Marsden wrote:
> 
>>This is a patch for Derby-250 to eliminate the conversion error when a
>>BigDecimal with more than
>>31 digits is  passed to setObject  with a targetSqlType.
>>public void setObject(int parameterIndex,
>>                      Object x,
>>                      int targetSqlType)
>>               throws SQLException
>>or
>>public void setObject(int parameterIndex,
>>                      Object x,
>>                      int targetSqlType,
>>                      int scale)
>>               throws SQLException
>>
>>The approach of the patch is to have setObject calls with a
>>targetSqlType  to always convert before sending to the value to the
>>server for all types.

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


Dan.


Mime
View raw message