db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2307) DatabaseMetaData.getTypeInfo nullability is incorrect for columns 1,7 and 9
Date Thu, 08 Feb 2007 18:25:05 GMT
DatabaseMetaData.getTypeInfo nullability is incorrect for columns 1,7 and 9
---------------------------------------------------------------------------

                 Key: DERBY-2307
                 URL: https://issues.apache.org/jira/browse/DERBY-2307
             Project: Derby
          Issue Type: Bug
          Components: JDBC, SQL
    Affects Versions: 10.2.2.0, 10.2.1.6, 10.1.3.1, 10.1.2.1, 10.1.1.0, 10.0.2.1, 10.0.2.0,
10.3.0.0
            Reporter: Daniel John Debrunner
            Priority: Minor


Columns TYPE_NAME, NULLABLE, SEARCHABLE are returned as nullable but should not be. ODBC variant
correctly makes these non-nullable.

>From a quick look at the metadata query this may in fact be a language issue. The query
is based upon a VALUES clauses that has a list of literals that are not NULL in these columns.
Thus one would expect the implied type definition to be not nullable. However some of the
columns, e.g. 2 DATA_TYPE, have a similar list of non-NULL literals are do appear as non-NULLABLE
with getTypeInfo. Not sure what leads to the different behaviour.

Look for comments in DatabaseMetaDataTest.testGetTypeInfo() with this bug number for code
t hat shows the issue.

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