[DERBY-3343] Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is "Generated always"

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.3.2.1
• Fix Version/s: 10.3.3.0, 10.4.1.3
• Component/s: SQL
• Environment: gentoo linux amd64
• Bug behavior facts: Regression
• Assignee: Dyre Tjeldvoll
• Reporter: William Becker
• Created: 23/Jan/08 03:12
• Updated: 21/Jan/11 17:51
• Resolved: 26/Jan/08 16:07

Description

The following series of statements fails:

j> connect 'jdbc:derby:test;create=true';
ij> create table t (id int primary key generated always as identity);
0 rows inserted/updated/deleted
ij> prepare p as 'insert into t(id) values (default)';
ij> execute p;
1 row inserted/updated/deleted
ij> execute p;
ERROR 23505: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL080123140906700' defined on 'T'.

There is a more detailed discussion about it here: http://www.nabble.com/Generate-Always-and-SQLIntegrityConstraintViolationException-td15012038.html#a15018054

Issue Links

• is related to: DERBY-827 Performance can be improved by re-using language ResultSets across Activation executions.