Bug #44471 Transactions do not persist across tabs
Submitted: 24 Apr 2009 19:40 Modified: 14 May 2009 11:10
Reporter: David Berg Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:All after 1.2.12 OS:Windows (XP Pro SP3)
Assigned to: CPU Architecture:Any

[24 Apr 2009 19:40] David Berg
In Versions 1.2.12 and prior, transactions persisted across tabs. In versions subsequent to 1.2.12, transactions no longer persist across tabs. I don't know what the intent of the developers is. Is this a bug or was it a bug fix?

The specific behavior is that in Versions 1.2.12 and prior, objects created within a transaction in one Script or Result Set tab are accessible in other Script or Result Set tabs. In versions subsequent to 1.2.12 they are not.

I typically use this behavior to test the results of scripts during their execution by setting break points and then viewing the progressive results in an adjacent tab. In versions subsequent to 1.2.12, I am no longer able to do that. If this is a bug that was introduced, I'd like to see it repaired. If that transactions persisted across tabs was a bug that was then fixed, I'd like to have an alternative to analyzing the progressive execution of scripts. Thank you.

How to repeat:
Perform the following in Query Browser Version 1.2.12 and then again in any subsequent version (1.2.17, e.g.).

Open a Script Tab.
Enter and execute the following script:

INSERT INTO tab1 VALUES (1), (2), (3);
SET @var1 = (SELECT col1 FROM tab1 WHERE col1 = 1);

Open a Result Set Tab.
Enter and execute each of the following statements:

select * from tab1;
select @var1;
drop table tab1;

In Version 1.2.12, the first statement selects the contents of tab1; the second selects the value contained in @var1; the third statement drops the table.

In versions subsequent to 1.2.12 (1.2.17, e.g.), each statement fails because the object being selected does not exist.
[14 May 2009 11:10] Susanne Ebrecht
Many thanks for writing a bug report.

Unfortunately this is not a bug. Transactions are just valid per session. You opened two sessions here and so you won't have the transaction from first session in your second session.

The old behaviour was a bug and a big security lack.