db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-584) Mismatch between DatabaseMetaData and ResultSetMetaData for NUMERIC type
Date Fri, 10 Jul 2009 21:33:14 GMT

     [ https://issues.apache.org/jira/browse/DERBY-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Matrigali updated DERBY-584:
---------------------------------

               Urgency: Normal
    Bug behavior facts: [Embedded/Client difference]

Triaged July 2, 2009: assigned normal urgency. 
I am guessing the difference is an embedded vs. client difference, but just a guess.

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message