Derby
  1. Derby
  2. DERBY-2307

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

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4
    • Fix Version/s: None
    • Component/s: JDBC, SQL
    • Urgency:
      Normal

      Description

      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

          Activity

          No work has yet been logged on this issue.

            People

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

              Dates

              • Created:
                Updated:

                Development