You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is bad, as it have unneeded error in status-vector :
DDL: CREATE TABLE T1 (ID INT)
DDL: CREATE UNIQUE INDEX T1_UQ ON T1 (ID)
DDL: COMMIT
tx1: SET TRANSACTION READ COMMITTED RECORD_VERSION NO WAIT
tx1: INSERT INTO T1 VALUES (1)
tx2: SET TRANSACTION READ COMMITTED RECORD_VERSION NO WAIT
tx2: INSERT INTO T1 VALUES (1)
lock conflict on no wait transaction
attempt to store duplicate value (visible to active transactions) in unique index "T1_UQ"
More, if someone tried to catch isc_no_dup and handle it in some way he well be in trouble.
Test Details: Confirmed on WI-V2.5.0.26074, STDERR was:
Statement failed, SQLSTATE = 40001
lock conflict on no wait transaction -- <<< !!! <<<
-violation of PRIMARY or UNIQUE KEY constraint "T_PK" on table "T"
Submitted by: @hvlad
This is bad, as it have unneeded error in status-vector :
DDL: CREATE TABLE T1 (ID INT)
DDL: CREATE UNIQUE INDEX T1_UQ ON T1 (ID)
DDL: COMMIT
tx1: SET TRANSACTION READ COMMITTED RECORD_VERSION NO WAIT
tx1: INSERT INTO T1 VALUES (1)
tx2: SET TRANSACTION READ COMMITTED RECORD_VERSION NO WAIT
tx2: INSERT INTO T1 VALUES (1)
lock conflict on no wait transaction
attempt to store duplicate value (visible to active transactions) in unique index "T1_UQ"
More, if someone tried to catch isc_no_dup and handle it in some way he well be in trouble.
Commits: 09b756b 6cdb30e f8c6908
====== Test Details ======
Confirmed on WI-V2.5.0.26074, STDERR was:
Statement failed, SQLSTATE = 40001
lock conflict on no wait transaction -- <<< !!! <<<
-violation of PRIMARY or UNIQUE KEY constraint "T_PK" on table "T"
The text was updated successfully, but these errors were encountered: