[DERBY-4777] Different behavior in Client and Embedded modes when update on an invalid cursor

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.7.1.1
• Fix Version/s: 10.7.1.1
• Component/s: JDBC
• Bug behavior facts: Embedded/Client difference
• Assignee: Yun Lee
• Reporter: Yun Lee
• Created: 16/Aug/10 11:57
• Updated: 17/Jun/13 09:19
• Resolved: 26/Aug/10 17:35

Description

Consider the sql snippet below:

create table test(c1 int, c2 int);
insert into test values(1,1);
update test set c1=2 where current of jdk4;

for the 'update' line, we get 'ERROR XJ202: Invalid cursor name 'JDK4'. ' in Client mode, while 'ERROR 42X30: Cursor 'JDK4' not found. Verify that autocommit is OFF.' in Embed mode.

Issue Links

• is part of: DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.
• is part of: DERBY-4609 Derby Test and Fix GSOC 2010 project
• is related to: DERBY-3801 Convert "org.apache.derbyTesting.functionTests.tests.lang.holdCursorIJ.sql" to junit.