[jira] Commented: (DERBY-2262) DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types

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