Issue Details (XML | Word | Printable)

Key: CORE-3394
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Vlad Khorsun
Reporter: Vlad Khorsun
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Firebird Core

Failed attempt to violate unique constraint could leave unneeded "lock conflict" error in status-vector

Created: 17/Mar/11 11:04 AM   Updated: 23/Apr/13 11:47 AM
Component/s: Engine
Affects Version/s: 2.5.0, 2.1.4
Fix Version/s: 2.5.1, 2.1.5, 3.0 Alpha 1

Time Tracking:
Not Specified

Planning Status: Unspecified


 Description  « Hide
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.

 All   Comments   Work Log   Change History   Version Control   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.