This release introduces a new major feature – GUI transaction support – as well as some minor features and bug fixes.
Changes as compared to MySQL GUI 12.2.6 include:
* GUI transactions support. This new feature is available in Enterprise and Ultimate editions. Also please see note below.
* Added a tooltip on column headers in Data tab informing about column name, column type and length. In Result tab the tooltip will display column name only, as the result returned by MySQL does not have information of storage type details.
* Added GUI support for index-level comments in CREATE/ALTER TABLE.
* Fixed an issue where GUI could ‘hang’ when executing queries with very large subqueries.
* Fixed an issue with the confirmation prompt in User Manager. It could appear when it should not and vice versa.
* Fixed a color rendering bug in Connection Manager.
* Multiple empty lines were made one when creating/altering a stored program.
* Duplicate table was not copying Virtual Columns of the table.
* Fixed a crash when reverting changes made to a newly defined table. Only HTTP-tunnel was affected.
* Fixed a crash occurring sometimes when selecting a table and inserting a DELETE statement into the editor from table menu .. Paste SQL Statement.
* Row-count for a table in INFO tab displayed as a number of “K”, “M” or G” rows using base-2 number system. Using this number system makes no sense in this context.
* Copy DB to a different host now identifies a DB on a target named the same as the source DB if such exists on target.
A note about the new GUI transactions support:
The new GUI transactions support adds a new category to the menu with complete support for transactional statements as well as icons/buttons for most common transactional operations: START TRANSACTION, COMMIT and ROLLBACK. This is however not the major achievement here. This alone would be pretty simple, actually. The major achievement is that the GUI is aware of the current ‘transactional state’ of a session and gives visual feedback to the user about this state – and does this no matter if a transactional statement was executed using the new GUI controls introduced in this release or executed from the editor. Note, however, that it is user’s responsibility to know the ‘transactional capabilities’ of the storage engines used. This new GUI functionality assumes ‘transactional capabilities’ identical to InnoDB for all tables.