SQLDecimal.getWholeDigits returns invalid result on JDK1.5.0

• Key: DERBY-74
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Unassigned
• Reporter: Jeremy Boynes
• Component/s: SQL
• Affects Version/s: 10.1.1.0
• Fix Version/s: 10.1.1.0

Description

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)

Comments

[Jeremy Boynes]

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

[Jeremy Boynes]

previous patch also fixed a couple of JavaDoc errors and unused imports in SQLDecimal.java

[Daniel John Debrunner]

Patch applied as-is.

Sending java/engine/org/apache/derby/iapi/types/SQLDecimal.java
Transmitting file data .
Committed revision 106329.

[Andrew McIntyre]

This issue has been resolved for over a year with no further movement. Closing.