db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-2262) DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types
Date Mon, 12 Mar 2007 08:51:13 GMT

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


Mime
View raw message