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

Wrong functionality of auto-generated keys support

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 10.3.2.1
    • None
    • Documentation, JDBC
    • N/A
    • Normal
    • High Value Fix, Repro attached
    • Deviation from standard

    Description

      Currently support for autogeneration key retrieval in JDBC driver (java.sql.Statement) relies on IDENTITY_VAL_LOCAL function, which means that for multi-row INSERT... VALUES statements as well as for INSERT...AS SELECT statement wrong result are returned (key generated of last executed single-row INSERT...VALUES statement or NULL otherwise). While this functionality is documented in the Reference description of IDENTITY_VAL_LOCAL it is not so clearly documented in "autogenerated keys" subchapter of JDBC 3.0 Features (the only vague hint is "Calling ResultSet.getMetaData on the ResultSet object returned by getGeneratedKeys produces a ResultSetMetaData object that is similar to that returned by IDENTITY_VAL_LOCAL.").

      Moreover, as far as I understant it diverge from JDBC specification. IMHO or this functionality shal lbe implemented completely, or exception shall be thrown if for given statement functionality is not supported (e.g. "Feature not supported").

      Attachments

        1. generated-keys.diff
          2 kB
          Knut Anders Hatlen
        2. TestGeneratedKeys.java
          3 kB
          Oleksandr Alesinskyy

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. DERBY-6994 Only last generated key in batch update is returned

          • Major - Major loss of function.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. DERBY-6934 Lock conflicts between Statement.getGeneratedKeys() and sequence-generator-based identity columns

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. DERBY-6952 Regression on Statement.getGeneratedKeys() on UPDATE statements

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. DERBY-6389 Update adminguide's list of differences between client and embedded

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. DERBY-5823 Multi-row insert fails on table without generated keys with RETURN_GENERATED_KEYS

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

          Bug - A problem which impairs or prevents the functions of the product. DERBY-6849 Statement.RETURN_GENERATED_KEYS returns a 1 row result set even if there are no auto-generated fields

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. DERBY-6948 INSERT .. SELECT produces NULL for getGeneratedKeys()

          • Major - Major loss of function.
          • Open

          Activity

            People

              Unassigned Unassigned
              al0 Oleksandr Alesinskyy
              Votes:
              6 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated: