[
https://issues.apache.org/jira/browse/DERBY-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-4777:
--------------------------------------
Affects Version/s: 10.7.0.0
Issue & fix info: [Release Note Needed] (was: [Patch Available])
Tests ran cleanly against classes (except for testPing/DERBY-4762) so I
committed the modified patch with revision 986750. Marking Release Note Needed
sothe issue will be flagged when we make a next release.
> perform different in Client and Embed modes when update on an invalid cursor
> ----------------------------------------------------------------------------
>
> Key: DERBY-4777
> URL: https://issues.apache.org/jira/browse/DERBY-4777
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 10.7.0.0
> Reporter: Yun Lee
> Assignee: Yun Lee
> Attachments: derby-4777.patch, derby-4777.stat, DERBY-4777_b.diff,
> DERBY-4777_b.stat
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
