MySQL Bugs: #18045: QB things it's in a transaction, when it in fact isn't.

Bug #18045	QB things it's in a transaction, when it in fact isn't.
Submitted:	7 Mar 2006 19:00	Modified:	3 Jan 2007 15:06
Reporter:	Tobias Asplund	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S2 (Serious)
Version:	1.1.20	OS:	Windows (Windows)
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	Generic

Description:
QB fails to handle manual "start transaction" commands properly.
It updates the buttons within QB to reflect that you are within a transaction, but under the hood disconnects the MySQL session.

You think you do your changes within a transaction, while they're in fact being autocommitted to the DB as you do them... you hit your rollback button in QB to undo changes... but... there's nothing to undo.

How to repeat:
type "START TRANSACTION" in the query window.
The transaction control buttons will shift to make the commit/rollback buttons highlighted and grey out the start transaction button.
But checking at the general query log we see:

060307 13:55:17	     49 Connect     root@ as anonymous on world
		     49 Query       SET SESSION interactive_timeout=1000000
		     49 Query       SELECT @@sql_mode
		     49 Query       SET SESSION sql_mode='STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'
		     49 Query       SET NAMES utf8
		     49 Query       SELECT @@SQL_MODE
		     49 Query       start transaction
		     49 Quit       

By quitting out, of course we're not in the transaction anymore.

Thank you for the bug report.

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html