Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-3171

ResultsetMetadata.isNullable returns different value for networkserver/client vs. embedded on some columns after a call to DatabaseMetaData.getAttributes()

    Details

    • Type: Bug
    • Status: Open
    • Priority: Trivial
    • Resolution: Unresolved
    • Affects Version/s: 10.4.1.3
    • Fix Version/s: None
    • Component/s: JDBC
    • Urgency:
      Normal
    • Issue & fix info:
      Newcomer, Repro attached
    • Bug behavior facts:
      Embedded/Client difference

      Description

      Code like the following:
      DatabaseMetaData dmd = <a connection>.getMetaData();
      ResultSet rs = dmd.getAttributes(null,null,null,null);
      ResultSetMetaData rsmd = rs.getMetaData();
      int actualCols = rsmd.getColumnCount();
      for (int i = 0; i < actualCols; i++)

      { System.out.println(rsmd.getColumnName(i+1)); System.out.println(rsmd.isNullable(i+1)); }

      Will return different values for a number of columns in the resultset for network server/client vs. embedded.
      See test fixture DatabaseMetaData.testUnimplementedSQLObjectAttributes().
      The difference shows up for: DATA_TYPE, ATTR_SIZE, DECIMAL_DIGITS, NUM_PREC_RADIX, NULLABLE, SQL_DATA_TYPE, SQL_DATETIME_SUB, CHAR_OCTET_LENGTH, ORDINAL_POSITION.

      It's unlikely that this would ever cause a problem for a user's application, so marking as trivial.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                myrna Myrna van Lunteren
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: