You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2006/01/20 02:27:42 UTC
[jira] Created: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
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
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
[jira] Commented: (DERBY-836)
ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for
DECIMAL columns
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=comments#action_12414544 ]
Daniel John Debrunner commented on DERBY-836:
---------------------------------------------
The code changes are fine but there are other tests, like odbc_metadata and upgrade, that use the same test code. Can you run the derbyall suite and provide a patch for the other master files that need to change?
> 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-v3.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
[jira] Commented: (DERBY-836)
ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for
DECIMAL columns
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=comments#action_12421532 ]
Andrew McIntyre commented on DERBY-836:
---------------------------------------
I've tried applying the -v7 patch on both Mac OS X and Cygwin, and in both cases, I get this:
patching file java/testing/org/apache/derbyTesting/functionTests/master/onlineBackupTest4.out
patch: **** malformed patch at line 440: &^M
I've set svn:eol-style native for onlineBackupTest4.out. Could you please 'svn up' and then regenerate your 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
> Fix For: 10.2.0.0
>
> Attachments: derby836-v2.diff, derby836-v3.diff, derby836-v4.diff, derby836-v6.diff, derby836-v7.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
Re: [jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by Daniel John Debrunner <dj...@apache.org>.
Mayuresh Nirhali (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-836?page=all ]
>
> Mayuresh Nirhali updated DERBY-836:
> -----------------------------------
>
> Attachment: derby836-v3.diff
>
> This patch was reviewed but not yet commited since last month.
>
> In the past few weeks, some files which were part of this patch were removed from the trunk. I am updating the patch here and hoping that this will be committed soon.
I will review (and commit) the new patch.
Dan.
[jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by "Mayuresh Nirhali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ]
Mayuresh Nirhali updated DERBY-836:
-----------------------------------
Attachment: derby836-v3.diff
This patch was reviewed but not yet commited since last month.
In the past few weeks, some files which were part of this patch were removed from the trunk. I am updating the patch here and hoping that this will be committed soon.
> 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-v3.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
[jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by "Mayuresh Nirhali (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ]
Daniel John Debrunner updated DERBY-836:
----------------------------------------
Priority: Minor (was: Major)
> 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
> Priority: Minor
>
> 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
[jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by "Mayuresh Nirhali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ]
Mayuresh Nirhali updated DERBY-836:
-----------------------------------
Attachment: derby836-v4.diff
Thanks daniel for the review.
As per the review comments, I have corrected the canon files for odbc_metadata and Upgrade tests.
The latest patch is now attached (version4) with this comment.
Once committed, I plan to have this patch ready for 10.1 branch for the 10.1.3 release.
> 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-v3.diff, derby836-v4.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
[jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by "Mayuresh Nirhali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ]
Mayuresh Nirhali updated DERBY-836:
-----------------------------------
Attachment: derby836-v6.diff
Thanks Dan for pointing out the error.
I have now added diffs for the master files which were failing due to this change and a complete patch is now attached as derby836-v6.diff.
> 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-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
[jira] Closed: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ]
Daniel John Debrunner closed DERBY-836.
---------------------------------------
Fix Version/s: 10.2.0.0
Resolution: Fixed
Committed revision 421932.
> 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
> Fix For: 10.2.0.0
>
> 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
[jira] Commented: (DERBY-836)
ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for
DECIMAL columns
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=comments#action_12415069 ]
Daniel John Debrunner commented on DERBY-836:
---------------------------------------------
Did you run derbyall to ensure there are no additional tests using the metadata class?
> 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-v3.diff, derby836-v4.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
[jira] Commented: (DERBY-836)
ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for
DECIMAL columns
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=comments#action_12421144 ]
Daniel John Debrunner commented on DERBY-836:
---------------------------------------------
Thanks Mayuresh for fixing this bug and having the patience to work through the test changes.
> 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
> Fix For: 10.2.0.0
>
> 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
[jira] Commented: (DERBY-836)
ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for
DECIMAL columns
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=comments#action_12363433 ]
Daniel John Debrunner commented on DERBY-836:
---------------------------------------------
Committed revision 370886 for the additional tests cases in jdbcapi/metadata.java
> 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
> Priority: Minor
>
> 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
Re: [jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by Bryan Pendleton <bp...@amberpoint.com>.
> Mayuresh Nirhali updated DERBY-836:
> -----------------------------------
>
> Attachment: derby836.diff
Thank you for contributing a patch for this problem.
Your patch applied cleanly for me, and I was able to reproduce
your results. With your new master files, but without your new
code changes, the metadata test fails with the expected diff, and
then when I included your code changes, the metadata test then
succeeds. I was successful re-running your test in both embedded
and network client.
However, I have two comments on your patch:
1) I found the comment that you added to the JIRA issue to be
easier to understand than the comment in the code, so I think
it would be nice if you would change the comment in the code to
match the comment in the JIRA issue. The JIRA issue comment is just
a little less terse and easier to understand, because it lays out
all three cases nicely.
2) You updated the master files for the DerbyNet framework, but
I believe that is incorrect, because you didn't fix the bug in
the JCC driver, only in the Network Client driver. So I think you
need to revert the DerbyNet master file changes and exclude them
from the patch, and I think it would be good to add a comment to
the JIRA issue indicating that this bug is present in the JCC
driver as well, but that we aren't (obviously) fixing it in that
driver.
thanks,
bryan
[jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by "Mayuresh Nirhali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ]
Mayuresh Nirhali updated DERBY-836:
-----------------------------------
Attachment: derby836.diff
There are 3 possible cases with respect to finding the correct maximum width for DECIMAL type.
1. If scale = 0, only sign should be added to precision to compute max width.
2. scale = precision, in this case 3 should be added to precision for sign, decimal and an additional char '0'.
3. precision > scale > 0, 2 shoud be added to precision for sign and decimal.
In the embedded codepath, Only first and third is implemented. The second case is implemented in the fix attached.
With respect to netclient codepath, only the third case is implemented. The fix attached does attempt to cover all the three..
Also, all the required canon files are modified to now test the fix with correct values.
> 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.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
[jira] Commented: (DERBY-836)
ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for
DECIMAL columns
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=comments#action_12419586 ]
Daniel John Debrunner commented on DERBY-836:
---------------------------------------------
I believe the failures you are seeing are due to the change. It's probably because the change in metadata information for DECIMAL columns is causing ij to display its output differently, causing the changes.
I ran functions.sql with and without the patch, it fails with the patch and passes without.
> 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-v3.diff, derby836-v4.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
[jira] Resolved: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ]
Knut Anders Hatlen resolved DERBY-836.
--------------------------------------
Resolution: Fixed
Thank you, Mayuresh! I have committed the v7_2 patch into trunk with revision 422706. Derbyall runs cleanly now.
> 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
> Fix For: 10.2.0.0
>
> Attachments: derby836-v2.diff, derby836-v3.diff, derby836-v4.diff, derby836-v6.diff, derby836-v7.diff, derby836-v7_2.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
[jira] Assigned: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by "Mayuresh Nirhali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ]
Mayuresh Nirhali reassigned DERBY-836:
--------------------------------------
Assign To: Mayuresh Nirhali
> 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
>
> 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
[jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by "Mayuresh Nirhali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ]
Mayuresh Nirhali updated DERBY-836:
-----------------------------------
Attachment: derby836-v7_2.diff
regenerated the patch as per andrew's comment.
> 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
> Fix For: 10.2.0.0
>
> Attachments: derby836-v2.diff, derby836-v3.diff, derby836-v4.diff, derby836-v6.diff, derby836-v7.diff, derby836-v7_2.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
[jira] Commented: (DERBY-836)
ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for
DECIMAL columns
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by "Mayuresh Nirhali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ]
Mayuresh Nirhali updated DERBY-836:
-----------------------------------
Attachment: derby836-v7.diff
After the commit of derby-v6 patch, 3 store tests and 5 nist tests failed in the nightly testruns.
These failures are due to missing canon file changes in the previous patch. I have created a new patch (not including the previous diffs) and is posted now.
All the store and nist tests pass with derby-v7.diff and this patch is ready to commit.
> 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
> Fix For: 10.2.0.0
>
> Attachments: derby836-v2.diff, derby836-v3.diff, derby836-v4.diff, derby836-v6.diff, derby836-v7.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
[jira] Reopened: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by "Mayuresh Nirhali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ]
Mayuresh Nirhali reopened DERBY-836:
------------------------------------
3 store tests and 5 nist tests fail due to minor canon file changes. Reopening this issue to make sure those issues are fixed.
> 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
> Fix For: 10.2.0.0
>
> 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
[jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize
sometimes returns wrong values for DECIMAL columns
Posted by "Mayuresh Nirhali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ]
Mayuresh Nirhali updated DERBY-836:
-----------------------------------
Attachment: derby836_v5.diff
I ran derbyall and found many failures. I ran it today again and still see some failures which does not seem related to derby-836. I also found 1 failure related to derby836 and have updated my patch (v5).
The failures i still see (but not related to derby836) are as below,
lang/aggbuiltin.sql
lang/aggregate.sql
lang/cast.sql
lang/casting.java
lang/compressTable.sql
lang/consistencyChecker.sql
lang/ejbql.sql
lang/floattypes.sql
lang/functions.sql
lang/implicitConversions.sql
lang/lojreorder.sql
lang/orderby.sql
lang/partdml.sql
lang/specjPlans.sql
lang/supersimple.sql
lang/triggerGeneral.sql
lang/triggerRefClause.sql
tools/derbyrunjartest.java
tools/importExportThruIJ.sql
tools/ieptests.sql
i18n/I18NImportExport.sql
i18n/urlLocale.sql
i18n/messageLocale.sql
i18n/iepnegativetests_ES.sql
upgradeTests/Upgrade_10_1_10_2.java
> 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-v3.diff, derby836-v4.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