[
https://issues.apache.org/jira/browse/DERBY-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291202#comment-13291202
]
Rick Hillegas commented on DERBY-5494:
--------------------------------------
Thanks for running the latest batch of experiments, Mamta. It is good to see
that, on your platform, the 10.9.1 defaults result in slightly better
throughput for sequences and identities than the previous 10.8.2 release.
Thanks.
> Same value returned by successive calls to a sequence generator flanking an
> unorderly shutdown.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-5494
> URL: https://issues.apache.org/jira/browse/DERBY-5494
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2,
> 10.9.1.0
> Reporter: Rick Hillegas
> Assignee: Mike Matrigali
> Labels: derby_backport_reject_10_8, derby_triage10_9
> Fix For: 10.9.1.0, 10.10.0.0
>
> Attachments: derby-5494_3.diff, derby-5494_diff_1a.txt,
> derby-5494_diff_2.txt
>
>
> The following sequence of steps causes a sequence generator to return the
> same value on successive NEXT VALUE FOR calls.
> 1) Bring up ij and issue the following commands:
> connect 'jdbc:derby:db;create=true';
> create sequence s;
> values next value for s;
> 2) Control-c out of ij so that the engine comes down hard without an orderly
> shutdown.
> 3) Now bring up ij again and issue the following commands:
> connect 'jdbc:derby:db';
> values next value for s;
> Thanks to Knut for finding this one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
