db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Boynes (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-74) SQLDecimal.getWholeDigits returns invalid result on JDK1.5.0
Date Mon, 22 Nov 2004 00:31:25 GMT
     [ http://nagoya.apache.org/jira/browse/DERBY-74?page=history ]

Jeremy Boynes updated DERBY-74:

    Attachment: derby_getWholeDigits_jdk15.patch

patch that stops the exception on insert
still passes derbylang tests with JDK1.4.2
however, text generated by ij is still different resulting in failures on JDK1.5.0

> SQLDecimal.getWholeDigits returns invalid result on JDK1.5.0
> ------------------------------------------------------------
>          Key: DERBY-74
>          URL: http://nagoya.apache.org/jira/browse/DERBY-74
>      Project: Derby
>         Type: Bug
>   Components: SQL
>  Environment: JDK1.5.0
>     Reporter: Jeremy Boynes
>  Attachments: derby_getWholeDigits_jdk15.patch
> With JDK1.5.0 the behaviour of BigDecimal.toString() has changed (thanks Sun) and for
numbers < 1e-6 it now returns a String in exponential syntax. This causes the number of
digits to be calculated incorrectly.
> As a result, the ejbql test fails as the following snippet fails:
> create table myDecimal (b DECIMAL(31,31))
> insert into myDecimal VALUES(1e-30)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message