MySQL Bugs: #49384: No ability to start transaction or set auto-commit in WB

Bug #49384	No ability to start transaction or set auto-commit in WB
Submitted:	2 Dec 2009 23:57	Modified:	8 Dec 2009 15:21
Reporter:	Todd Farmer (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.10 r4680	OS:	Windows (XP)
Assigned to:	Sergei Tkachenko	CPU Architecture:	Any

Description:
Unlike in QB, which defaults to auto-commit on, but lets you explicitly start a transaction and subsequently commit/rollback, WB only has the option for commit and rollback.  Everything is executed with auto-commit off, and there appears to be no option to enable auto-commit, or to explicitly start a transaction, as there was in QB.

For my part, I expected WB to behave like QB, and that my executed statements were being committed.

Furthermore, the data viewer/editor *does* commit when saving the data, which seems inconsistent with the way the SQL interface works.

How to repeat:
See above.

Suggested fix:
Provide start transaction button
Default to auto-commit on
Disable commit/rollback unless in a transaction

Added toolbar toggle button to enable/disable auto-commit mode.
Now auto-commit mode is on by default.
Disabled commit/rollback toolbar button when not applicable.

fix/changes confirmed as described by developer.
will be included in 5.2.11

info for documentation: please include the new behavior (auto-commit on per default) and the new functionality (autocommit-toggle-button) in docs

A note will be added to the main documentation in due course.

An entry has been added to the 5.2.11 changelog:

MySQL Workbench did not have the ability to toggle Autocommit mode, or a facility to explicitly start a transaction, in the SQL Editor. This was in contrast to Query Browser, which did support such facilities.