[
https://issues.apache.org/jira/browse/DERBY-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-4777:
---------------------------------
Attachment: releaseNote.html
Updating the release note, incorporating feedback from Dag on the 10.7.1
release notes.
> Different behavior in Client and Embedded 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.1.0
> Reporter: Yun Lee
> Assignee: Yun Lee
> Fix For: 10.7.1.0
>
> Attachments: derby-4777-releasenote.patch,
> derby-4777-releasenote.stat, derby-4777.patch, derby-4777.stat,
> DERBY-4777_b.diff, DERBY-4777_b.stat, releaseNote.html, releaseNote.html
>
>
> 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.
