Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-141 Derby metadata doesn't agree with JDBC specification in some ways.
  3. DERBY-142

ResultSetMetaData.isReadOnly() also returns wrong results

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 10.0.2.1
    • None
    • JDBC
    • Using DB2 universal driver with standalone derby server
    • Normal
    • Repro attached
    • Deviation from standard, Embedded/Client difference

    Description

      ResultSetMetaData.isReadOnly() always returns true, even when writing to the table is possible.
      The JDBC 2.0 spec says: "ResultSetMetaData.isReadOnly() : Indicates whether the designated column is definitely not writable.", so the method should return false for a table.

      I will attach a testcase for this behaviour.

      Attachments

        1. TorqueTutorial.txt
          7 kB
          Jean T. Anderson
        2. DerbyTest142.java
          8 kB
        3. DerbyTest.java
          4 kB
          Thomas Fox

        Issue Links

          relates to

          Improvement - An improvement or enhancement to an existing feature or task. DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              Unassigned Unassigned
              tfischer Thomas Fox
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: