[
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.
