db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-160) Foreign key constraint failure closes the cursors in embedded mode but not in Network Server mode
Date Fri, 04 Mar 2005 19:12:46 GMT
Foreign key constraint failure closes the cursors in embedded mode but not in Network Server

         Key: DERBY-160
         URL: http://issues.apache.org/jira/browse/DERBY-160
     Project: Derby
        Type: Bug
  Components: Network Server  
    Reporter: Mamta A. Satoor

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
create table tableWithConstraint (c1 int, c2 int, constraint fk foreign key(c1,c2) references
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:
-- 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;

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message