Derby
  1. Derby
  2. DERBY-160

Foreign key constraint failure closes the cursors in embedded mode but not in Network Server mode

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 10.0.2.1
    • Fix Version/s: None
    • Component/s: Network Server
    • Urgency:
      Normal
    • Issue & fix info:
      Repro attached
    • Bug behavior facts:
      Embedded/Client difference

      Description

      When running embedded Derby in autocommit true mode(default), a foreign key violation closes the open cursors. But the cursors remain open after the foreign key violation when Derby is running in Network Server. Following code can be tried in ij for embedded and network server to see the behavior difference.

      create table tableWithPrimaryKey (c1 int not null, c2 int not null, constraint pk primary key(c1,c2));
      create table tableWithConstraint (c1 int, c2 int, constraint fk foreign key(c1,c2) references tableWithPrimaryKey);
      create table t1 (c11 int, c12 int);
      insert into t1 values (1,1), (2,2), (3,3);
      insert into tableWithPrimaryKey values (1, 1), (2, 2), (3, 3), (4, 4);
      insert into tableWithConstraint values (1, 1), (2, 2), (3, 3), (4, 4);
      get cursor c1 as 'select * from t1';
      next c1;
      – In both embedded and Network server modes, delete below will throw exception "ERROR 23503: DELETE on
      – table 'TABLEWITHPRIMARYKEY' caused a violation of foreign key constraint 'FK' for key (1,1).
      – The statement has been rolled back."
      delete from tableWithPrimaryKey;
      – In embedded mode, next on cursor below throws exception "ERROR XCL16: ResultSet not open, operation 'next' not
      – permitted. Verify that autocommit is OFF." But in Network Server mode, the cursor is still open and
      – next c1 spits out contents of next row.
      next c1;

        Issue Links

          Activity

          Hide
          Eduardo Pérez Ureta added a comment -

          I started developing an application using Apache Derby Embedded and hit this issue that I need working.
          I have seen this critical issue has been open for more than 3 years.
          I would like to know if you think this issue should be fixed or maybe it is not that important.
          I would like to know if closing all the cursors is something you expect or maybe it is a bug because I do not know why closing all the cursors gives any value.

          Show
          Eduardo Pérez Ureta added a comment - I started developing an application using Apache Derby Embedded and hit this issue that I need working. I have seen this critical issue has been open for more than 3 years. I would like to know if you think this issue should be fixed or maybe it is not that important. I would like to know if closing all the cursors is something you expect or maybe it is a bug because I do not know why closing all the cursors gives any value.
          Hide
          Myrna van Lunteren added a comment -

          the repro is actually included in the description.

          Show
          Myrna van Lunteren added a comment - the repro is actually included in the description.
          Hide
          Myrna van Lunteren added a comment -

          Although there's a difference between embedded and network server it seems to me either way could be seen as acceptable...
          Or is there a standard/spec reference that clearly states the cursors should be closed?
          I can also imagine an application could work-around this by doing a check on a delete failing and just not do the next, making sure it always works the same way - whether with embedded or NetworkServer.

          Because of these two reasons, I marked the urgency 'normal'.

          Eduardo - in case you're still interested...
          This is classified as 'Major' (the default priority), not 'Critical'. It's not a crash, and not incorrect data returned, and I think it has a possible workaround, so I think the priority is correct and the urgency is normal...
          I checked the archives and noticed you also sent a message to derby-user that went unanswered. Normally our community tries to be more responsive than that...

          If you are still interested and find this a critical issue, you could 'vote' for it which would increase the impact the community gives to it. Or you could attempt to address it yourself. If you'd like that, you can start by reading: http://wiki.apache.org/db-derby/ForNewDevelopers and link to: http://wiki.apache.org/db-derby/DerbyCommitProcess.

          Show
          Myrna van Lunteren added a comment - Although there's a difference between embedded and network server it seems to me either way could be seen as acceptable... Or is there a standard/spec reference that clearly states the cursors should be closed? I can also imagine an application could work-around this by doing a check on a delete failing and just not do the next, making sure it always works the same way - whether with embedded or NetworkServer. Because of these two reasons, I marked the urgency 'normal'. Eduardo - in case you're still interested... This is classified as 'Major' (the default priority), not 'Critical'. It's not a crash, and not incorrect data returned, and I think it has a possible workaround, so I think the priority is correct and the urgency is normal... I checked the archives and noticed you also sent a message to derby-user that went unanswered. Normally our community tries to be more responsive than that... If you are still interested and find this a critical issue, you could 'vote' for it which would increase the impact the community gives to it. Or you could attempt to address it yourself. If you'd like that, you can start by reading: http://wiki.apache.org/db-derby/ForNewDevelopers and link to: http://wiki.apache.org/db-derby/DerbyCommitProcess .
          Hide
          Knut Anders Hatlen added a comment -

          JDBC 4 added a new meta-data call to tell how the drivers behave on error: DatabaseMetaData.autoCommitFailureClosesAllResultSets(). The embedded driver returns true and the client driver returns false. See DERBY-3422.

          Show
          Knut Anders Hatlen added a comment - JDBC 4 added a new meta-data call to tell how the drivers behave on error: DatabaseMetaData.autoCommitFailureClosesAllResultSets(). The embedded driver returns true and the client driver returns false. See DERBY-3422 .

            People

            • Assignee:
              Unassigned
              Reporter:
              Mamta A. Satoor
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development