[DERBY-5493] Same value returned by successive calls to a sequence generator.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2, 10.9.1.0
• Fix Version/s: 10.9.1.0
• Component/s: SQL
• Labels: derby_backport_reject_10_8 derby_triage10_9
• Urgency: Normal
• Issue & fix info: Patch Available, Release Note Needed
• Bug behavior facts: Deviation from standard, Wrong query result
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 07/Nov/11 13:57
• Updated: 14/Jun/13 17:19
• Resolved: 20/Apr/12 17:15

Description

The following script shows the same value being returned from a sequence generator by two successive NEXT VALUE FOR calls. Thanks to Knut for finding this:

connect 'jdbc:derby:memory:db;create=true';

create table t (x int);
create sequence s;
autocommit off;
select count from sys.syssequences with rs;
values next value for s;
drop table t;
rollback;

– same value as previous call
values next value for s;

Issue Links

• is related to: DERBY-5495 Master issue to track fixes to sequence generators
• is related to: DERBY-4437 Concurrent inserts into table with identity column perform poorly
• is related to: DERBY-5697 Doc changes to account for correctness fixes for sequences