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

Incorrect handling when using an UPDATE to SET an identity column to DEFAULT

    XMLWordPrintableJSON

    Details

    • Urgency:
      Normal
    • Issue & fix info:
      Release Note Needed, Repro attached
    • Bug behavior facts:
      Deviation from standard

      Description

      Derby violates the SQL Standard when an UPDATE statement SETs an identity column to the value DEFAULT. Derby does the right thing for INSERTs, however.

      For INSERTs, the 2011 Standard defines the meaning of DEFAULT in part 2, section 15.10 (Effect of inserting tables into base tables), general rule 2. For INSERTs, the DEFAULT value is the next value of the sequence generator which defines the identity column.

      For UPDATEs, the 2011 Standard defines the meaning of DEFAULT in part 2, section 15.13 (Effect of replacing rows in base tables), general rule 5. For UPDATEs, the DEFAULT value is also the next value of the sequence generator which defines the identity column.

      Note also that the 2011 Standard says that a GENERATED ALWAYS identity column can be SET to DEFAULT. Furthermore, that is the only explicit value accepted. See the 2011 Standard, part 2, section 14.15 (set clause list), syntax rule 5:

      {
      "If <set clause> SC specifies an <object column> that references a column of which some underlying column is either a generated column or an identity column whose descriptor indicates that values are always generated, then the <update source> specified in SC shall consist of a <default specification>."
      }

      What Derby actually does for UPDATEs is the following:

      1) If the column was declared GENERATED ALWAYS, then Derby raises a compile-time error saying that the value of an identity column can't be overridden.

      2) If the column was declared GENERATED BY DEFAULT, then Derby raises an execution time-error when trying to stuff a null into the column.

      Correcting this bug would result in backwardly incompatible behavior. However, I think that the incompatibility is minor: it would mean the successful run of statements which previously raised errors.

      I tripped across this problem while implementing the UPDATE action of the MERGE statement (DERBY-3155). If we decide to fix this bug, we will want to make sure that the UPDATE actions of MERGE statements also correctly handle DEFAULT values for identity columns.

      The following script shows this problem:

      connect 'jdbc:derby:memory:db;create=true';

      create table t1( a int generated always as identity, b int );
      create table t2( a int generated by default as identity, b int );

      insert into t1( a, b ) values ( default, 100 );
      insert into t2( a, b ) values ( default, 100 );

      update t1 set a = default;
      update t2 set a = default;

      select * from t1;
      select * from t2;

        Attachments

        1. releaseNote.html
          4 kB
          Mamta A. Satoor
        2. releaseNote.html
          2 kB
          Richard N. Hillegas
        3. DERBY6414_patch2_stat.txt
          1 kB
          Mamta A. Satoor
        4. DERBY6414_patch2_diff.txt
          59 kB
          Mamta A. Satoor
        5. DERBY6414_patch1_stat.txt
          1.0 kB
          Mamta A. Satoor
        6. DERBY6414_patch1_notReadyForCommit_diff.txt
          0.9 kB
          Mamta A. Satoor
        7. DERBY6414_patch1_diff.txt
          49 kB
          Mamta A. Satoor
        8. d6414-reduce-visibility.diff
          1 kB
          Knut Anders Hatlen

          Issue Links

            Activity

              People

              • Assignee:
                mamtas Mamta A. Satoor
                Reporter:
                rhillegas Richard N. Hillegas
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: