Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.
  3. DERBY-2430

setObject(int targetType, Blob source) and setObject(int targetType, Clob source) should disallow updates on all targetTypes except BLOB and CLOB respectively

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 10.3.1.4
    • Network Client
    • None
    • All
    • Release Note Needed

    Description

      updateBlob(int columnIndex, Blob x), updateClob(int columnIndex, Clob x) can be implemented by forwarding calls to setObject(int targetType, Blob source), setObject(int targetType, Clob source). If this this done then

      1) updateClob on a CHAR/VARCHAR/LONG VARCHAR column throws an exception on the Embedded Driver but not on the NetworkClient
      2) updateBlob works on a CHAR/VARCHAR/LONG VARCHAR FOR BIT DATA throws an exception on the Embedded Driver but not on the NetworkClient

      From what the JDBC 4.0 spec says (pg 198 table b-5) the Embedded behaviour seems to be correct.

      This can be fixed by Matching Embedded behaviour. This would involve throwing an exception in the cases mentioned above

      Attachments

        1. releaseNote.html
          4 kB
          Richard N. Hillegas
        2. releaseNote.html
          4 kB
          Richard N. Hillegas
        3. releaseNote.html
          4 kB
          V.Narayanan
        4. setObjectForClobBlob_v1.diff
          6 kB
          V.Narayanan
        5. setObjectForClobBlob_v1.stat
          0.3 kB
          V.Narayanan

        Issue Links

          Activity

            People

              narayanan V.Narayanan
              narayanan V.Narayanan
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: