1. Derby
  2. DERBY-2307

DatabaseMetaData.getTypeInfo nullability is incorrect for columns 1,7 and 9


    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s:,,,,,,,
    • Fix Version/s: None
    • Component/s: JDBC, SQL
    • Urgency:


      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.

        Issue Links


          Daniel John Debrunner created issue -
          Saurabh Vyas made changes -
          Field Original Value New Value
          Link This issue blocks DERBY-2280 [ DERBY-2280 ]
          Rick Hillegas made changes -
          Urgency Normal
          Kathey Marsden made changes -
          Labels derby_triage10_5_2
          Gavin made changes -
          Link This issue blocks DERBY-2280 [ DERBY-2280 ]
          Gavin made changes -
          Link This issue is depended upon by DERBY-2280 [ DERBY-2280 ]
          Gavin made changes -
          Workflow jira [ 12396127 ] Default workflow, editable Closed status [ 12802256 ]


            • Assignee:
              Daniel John Debrunner
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created: