[
https://issues.apache.org/jira/browse/DERBY-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730882#action_12730882
]
Myrna van Lunteren commented on DERBY-160:
------------------------------------------
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.
> Foreign key constraint failure closes the cursors in embedded mode but not in
> Network Server mode
> -------------------------------------------------------------------------------------------------
>
> Key: DERBY-160
> URL: https://issues.apache.org/jira/browse/DERBY-160
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.0.2.1
> 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 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;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
