[
https://issues.apache.org/jira/browse/DERBY-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-4777:
--------------------------------------
Attachment: releaseNote.html
Thanks for that releaseNote.
On the whole, it looks good.
However, release notes don't need to be appended as 'patches'/svn diffs.
Instead, the templates/releaseNote.html is supposed to get copied to a
temporary location, not actually changed, and then copied, modified file can be
attached to the jira issue without a name change.
The flag 'release Note needed' stays on, the bug gets closed, and during the
next release cycle, the file 'releaseNote.html' attached to the issue will
automatically be included in the list of items requiring a release note.
I'm attaching the releaseNote.html resulting from your patch (I applied the
patch, copied the file, then reverted the
tools/release/templates/releaseNote.html).
I made a couple of tiny changes to the phrasing, nothing important.
> 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.0.0
> Reporter: Yun Lee
> Assignee: Yun Lee
> 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
>
>
> 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.
