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)" <ji...@apache.org> on 2007/01/22 18:17:30 UTC
[jira] Created: (DERBY-2262) DatabaseMetaData.getTypeInfo returns
incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
------------------------------------------------------------------------------------------------
Key: DERBY-2262
URL: https://issues.apache.org/jira/browse/DERBY-2262
Project: Derby
Issue Type: Bug
Components: JDBC
Affects Versions: 10.2.2.0, 10.2.1.6, 10.1.3.1, 10.1.2.1, 10.1.1.0, 10.3.0.0
Reporter: Daniel John Debrunner
Priority: Minor
Maximum scale is returned as 32767 but maximum scale for numerics is 31.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-2262) DatabaseMetaData.getTypeInfo returns
incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
Posted by "Saurabh Vyas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Saurabh Vyas updated DERBY-2262:
--------------------------------
Derby Info: [Patch Available]
> DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-2262
> URL: https://issues.apache.org/jira/browse/DERBY-2262
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Saurabh Vyas
> Priority: Minor
> Attachments: Derby-2262_v1.diff, Derby-2262_v1.stat
>
>
> Maximum scale is returned as 32767 but maximum scale for numerics is 31.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2262) DatabaseMetaData.getTypeInfo returns
incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-2262:
-----------------------------------
Attachment: Derby-2262_v3.diff
Removed tabs from the test code (surrounding code didn't use tabs) and shortened the comment to stay below 80 characters per line.
Uploaded version 3 of the patch.
> DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-2262
> URL: https://issues.apache.org/jira/browse/DERBY-2262
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Saurabh Vyas
> Priority: Minor
> Attachments: Derby-2262_v1.diff, Derby-2262_v1.stat, Derby-2262_v2.diff, Derby-2262_v3.diff
>
>
> Maximum scale is returned as 32767 but maximum scale for numerics is 31.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2262) DatabaseMetaData.getTypeInfo returns
incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
Posted by "Saurabh Vyas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Saurabh Vyas updated DERBY-2262:
--------------------------------
Attachment: Derby-2262_v2.diff
Thanks Krisitan for looking at the patch & your valuable comments.
Well in Derby-2262_v2.diff I had incorporated the changes suggested & ran JUnit jdbcapi suite which was successful.
> DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-2262
> URL: https://issues.apache.org/jira/browse/DERBY-2262
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Saurabh Vyas
> Priority: Minor
> Attachments: Derby-2262_v1.diff, Derby-2262_v1.stat, Derby-2262_v2.diff
>
>
> Maximum scale is returned as 32767 but maximum scale for numerics is 31.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-2262) DatabaseMetaData.getTypeInfo returns
incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan resolved DERBY-2262.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Derby Info: (was: [Patch Available])
Committed 'Derby-2262_v3.diff' to trunk with revision 517132.
This patch cannot be back-ported to 10.2 without modifications. My guess is the test has been renamed (or rewritten to JUnit).
> DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-2262
> URL: https://issues.apache.org/jira/browse/DERBY-2262
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Saurabh Vyas
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: Derby-2262_v1.diff, Derby-2262_v1.stat, Derby-2262_v2.diff, Derby-2262_v3.diff
>
>
> Maximum scale is returned as 32767 but maximum scale for numerics is 31.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2262) DatabaseMetaData.getTypeInfo returns
incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
Posted by "Saurabh Vyas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Saurabh Vyas updated DERBY-2262:
--------------------------------
Attachment: Derby-2262_v1.stat
Derby-2262_v1.diff
Corrected the Max Scale for Decimal & Numeric data type & correspondingly modified the test (DatabaseMetaDataTest.java) to expect the new corrected value.
> DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-2262
> URL: https://issues.apache.org/jira/browse/DERBY-2262
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Saurabh Vyas
> Priority: Minor
> Attachments: Derby-2262_v1.diff, Derby-2262_v1.stat
>
>
> Maximum scale is returned as 32767 but maximum scale for numerics is 31.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-2262) DatabaseMetaData.getTypeInfo returns
incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
Posted by "Saurabh Vyas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Saurabh Vyas reassigned DERBY-2262:
-----------------------------------
Assignee: Saurabh Vyas
> DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-2262
> URL: https://issues.apache.org/jira/browse/DERBY-2262
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Saurabh Vyas
> Priority: Minor
>
> Maximum scale is returned as 32767 but maximum scale for numerics is 31.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2262) DatabaseMetaData.getTypeInfo returns
incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479593 ]
Kristian Waagan commented on DERBY-2262:
----------------------------------------
I'm running tests for the patch ('Derby-2262_v1.diff').
If everything runs fine, I will commit as soon as possible to trunk and then back-port to 10.2. Let me know if I should not back-port.
I would appreciate if you fixed the two tabs in the test (mixed with spaces), and I'm a bit unsure about the "big" comment about this bug report in the test code.
What about removing the big one and maybe just add a short reference to this Jira at the end of the line?
If some special handling had been required to avoid/fix the bug, I agree big comment would be in place.
> DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-2262
> URL: https://issues.apache.org/jira/browse/DERBY-2262
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Saurabh Vyas
> Priority: Minor
> Attachments: Derby-2262_v1.diff, Derby-2262_v1.stat
>
>
> Maximum scale is returned as 32767 but maximum scale for numerics is 31.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.