[ http://issues.apache.org/jira/browse/DERBY-836?page=all ]
Mayuresh Nirhali updated DERBY-836:
-----------------------------------
Attachment: derby836-v2.diff
Thanks to Bryan, for reviewing my earlier patch.
As he has pointed out in the patch, previous patch has the master files under
DerbyNet updated, which is wrong. These files are used for testing the JCC
driver and this bug does exist in the JCC driver which needs to be fixed, hence
the change to those master files are differed now and they must be done when
the JCC driver is fixed.
Also, I have updated the comments in the code (that I changed) to be more
descriptive.
The attached file, derby836-v2.diff is now the latest patch.
> ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for
> DECIMAL columns
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-836
> URL: http://issues.apache.org/jira/browse/DERBY-836
> Project: Derby
> Type: Bug
> Components: JDBC, Newcomer
> Versions: 10.2.0.0
> Reporter: Daniel John Debrunner
> Assignee: Mayuresh Nirhali
> Priority: Minor
> Attachments: derby836-v2.diff, derby836.diff
>
> DECIMAL(10,0)
> max display width value: -1234567890 length 11
> embedded : 11 correct
> client: 12 WRONG
> DECIMAL(10,10)
> max display width value: -0.1234567890 length 13
> embedded : 13 correct
> client: 12 WRONG
> DECIMAL(10,2)
> max display width value: -12345678.90 length 12
> embedded : 13 WRONG
> client: 12 correct
> I've added output early on in jdbcapi/metadata_test.java (and hence the tests
> metadata.jar and odbc_metadata.java) to show this issue:
> E.g. for embedded
> DECIMAL(10,0) -- precision: 10 scale: 0 display size: 12 type name: DECIMAL
> DECIMAL(10,10) -- precision: 10 scale: 10 display size: 12 type name: DECIMAL
> DECIMAL(10,2) -- precision: 10 scale: 2 display size: 12 type name: DECIMAL
> I will add this test output once DERBY-829 is fixed so as not to cause
> conflicts.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
