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

Derby

Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is "Generated always"

Created: 23/Jan/08 03:12 AM Updated: 30/Jun/09 03:55 PM

Return to search

Component/s:

SQL

Affects Version/s:

10.3.2.1

Fix Version/s:

10.3.3.0, 10.4.1.3

Time Tracking:

Not Specified

File Attachments:

File Name	Date Attached	Attached By	Size
d3343.diff	2008-01-23 10:55 AM	Knut Anders Hatlen	0.9 kB
d3343.v2.diff	2008-01-25 08:05 AM	Dyre Tjeldvoll	4 kB
d3343.v3.diff	2008-01-25 10:24 AM	Dyre Tjeldvoll	4 kB
defaults.sql	2008-01-23 04:07 PM	Dyre Tjeldvoll	5 kB

Environment:

gentoo linux amd64

Issue Links:

Reference

This issue is related to:

~~DERBY-827~~ Performance can be improved by re-using language ResultSets across Activation executions.

Bug behavior facts:	Regression
Resolution Date:	26/Jan/08 04:07 PM

Description

« Hide

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

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

No work has yet been logged on this issue.