db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-584) Mismatch between DatabaseMetaData and ResultSetMetaData for NUMERIC type
Date Thu, 03 Mar 2011 22:14:36 GMT

    [ https://issues.apache.org/jira/browse/DERBY-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002278#comment-13002278
] 

Rick Hillegas commented on DERBY-584:
-------------------------------------

As a first cut at testing a fix for this issue, try running DatabaseMetaDataTest and the compatibility
tests. When those run cleanly, you should try the full regression test suite.

> Mismatch between DatabaseMetaData and ResultSetMetaData for NUMERIC type
> ------------------------------------------------------------------------
>
>                 Key: DERBY-584
>                 URL: https://issues.apache.org/jira/browse/DERBY-584
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions: 10.1.1.0
>            Reporter: Rick Hillegas
>              Labels: derby_triage10_5_2
>
> The Derby Reference Manual says that NUMERIC is a synonyn for DECIMAL. If you create
a NUMERIC column, the Derby client DatabaseMetaData reports that the type is java.sql.NUMERIC.
However, if you select from the table, the ResultSetMetaData reports that the type is java.sql.DECIMAL.
> I don't really care what type we report. I just think we should be consistent.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message