[ http://issues.apache.org/jira/browse/DERBY-836?page=comments#action_12421129 ] Daniel John Debrunner commented on DERBY-836: ---------------------------------------------
Does derbyall run cleanly with derby836-v6.diff patch? > ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for > DECIMAL columns > ----------------------------------------------------------------------------------------- > > Key: DERBY-836 > URL: http://issues.apache.org/jira/browse/DERBY-836 > Project: Derby > Issue Type: Bug > Components: JDBC, Newcomer > Affects Versions: 10.2.0.0 > Reporter: Daniel John Debrunner > Assigned To: Mayuresh Nirhali > Priority: Minor > Attachments: derby836-v2.diff, derby836-v3.diff, derby836-v4.diff, > derby836-v6.diff, derby836.diff, derby836_v5.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
