New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent results when working with GLOBAL TEMPORARY TABLE ON COMMIT PRESERVE ROWS [CORE5837] #6098
Comments
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Commented by: @hvlad To reproduce one need a database with one GTT and two isql sessions. GLOBAL TEMPORARY TABLE GTT (ID INT) ON COMMIT PRESERVE ROWS Case 1:
===================== 2>
===================== 1> 2>
===================== commit; 1>
===================== select first 1 * from gtt;
============ insert into gtt values (3); Firebird log contains message with bugcheck 185:
|
Commented by: @hvlad Case 2: 1>
===================== 2>
===================== 1> 2> 1> 2>
===================== commit; 1> Statement failed, SQLSTATE = 08001 Firebird log contains message with bugcheck 186:
|
Commented by: @hvlad Fix confirmed by user after week of testing |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Beta 1 [ 10750 ] Fix Version: 3.0.4 [ 10863 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Done successfully Test Details: Test was splitted on two parts (to be sure that no affect can occur from 1st to 2nd when they run) |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @hvlad
One attachment could see data of GTT instance of another attachment.
Bugcheck 185 or 186 could happens on rollback if transaction works with some GTT.
GTT here is GLOBAL TEMPORARY TABLE ON COMMIT PRESERVE ROWS.
GLOBAL TEMPORARY TABLE ON COMMIT DELETE ROWS is not affected.
Commits: 4defdea eca3fc6
====== Test Details ======
Test was splitted on two parts (to be sure that no affect can occur from 1st to 2nd when they run)
The text was updated successfully, but these errors were encountered: