db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2307) DatabaseMetaData.getTypeInfo nullability is incorrect for columns 1,7 and 9
Date Wed, 02 May 2007 17:58:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493159

A B commented on DERBY-2307:

Silly question: how do we know that these columns are supposed to be NON-nullable?  Is this
indicated by the fact that they do *not* have the words "may be null" after them in the API?
 Or is this being pulled from somewhere else (ex. the JDBC spec?)

> 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:,,,,,,,
>            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.

View raw message