This section documents all changes and bug fixes applied since the release of 5.2.10.
MySQL Workbench had confusing and erroneous behavior when attempting to handle multiple model tabs. It has now been changed so that if a model is currently loaded, and a new model or saved model needs to be loaded, the current model will be closed first before then opening the new model. (Bug #49422)
In the configuration editor, it was not possible to find, and therefore set, the configuration variable “old”.
This has now been added to the General tab in the configuration editor of the Admin tab. (Bug #49039)
It was impossible to use a function call as a field value in an
editable result set, such as for a result set in the Query
Editor or in the Inserts tab in the Table
Editor. This was because MySQL Workbench automatically escaped
string parameters passed to the function call. For example, if
an attempt was made to enter into a field a function such as
md5('fred'), MySQL Workbench would generate the
MySQL Workbench now makes it possible to enter a function, or any
other expression, into a field using the
\func prefix. For example,
md5('fred') can be entered. MySQL Workbench will now
ensure that the string 'fred' is not escaped. See
Security Fix: When using the Data Dump facility in the Admin screen, the full mysqldump command, including the password used, was written to the logs. (Bug #49294)
In the SQL Editor the SQL Statements area could only display ten lines of code and was not resizeable. (Bug #49788)
In an EER diagram, if the model was synchronized with a live database, any foreign key relationship lines that were set to hidden became visible. (Bug #49631)
In the Home screen Workspace, in the central panels listing connections, models and server instances, the items in the panels appeared to be rendered as links. However, clicking these “links” had no effect, and the items could only be loaded by double-clicking.
MySQL Workbench has been changed to remove the link effect, and these items can only be loaded by double-clicking. (Bug #49623)
When MySQL Workbench silently reconnected to a server after a communication failure, it failed to reinitialize the connection correctly. As a result of this failure Autocommit was silently enabled. If a user was working with transactional tables, the commit and rollback toolbar buttons appeared to work, although they had no effect. (Bug #49462)
If a connection failed MySQL Workbench reconnected silently. This
caused problems with transactions. If changes were made to a
table, before a
COMMIT, and the connection
lost, MySQL Workbench would reconnect silently and enable the user
COMMIT. However, it did not warn that this
COMMIT was on a new connection, and that the
COMMIT would have no effect.
In the Advanced tab of the configuration
editor, the option Delay key write had a
file selector button associated with it. This should have been a
list offering the values
When using the Create a new server instance wizard, the panel used to enter the SSH password was hidden by the wizard. (Bug #49416)
If the Home screen was closed and then an attempt made to reopen it from the View, Home main menu option, MySQL Workbench crashed. (Bug #49388)
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. (Bug #49384)
When using the Reverse Engineer SQL Script to import the Sakila
sakila-data.sql, MySQL Workbench
In the History tab of the SQL Editor, it was possible to simultaneously select multiple entries in the Time panel. However, this did not seem to serve any useful purpose as the content of the SQL column only displayed the code for a single entry. (Bug #49375)
In the Schemata Palette of the SQL Editor the default schema selector did not work if the schema name contained a '.' character. (Bug #49373)
When using the SQL Snippets palette, right-clicking a snippet, and then selecting the menu item Insert text into SQL Area, replaced all text in the SQL Statements area. This happened after another snippet had previously been inserted because the default state was to leave all code in the SQL Statements area selected. (Bug #49370)
AUTHORS file in the MySQL Workbench
distribution was empty.
In the Overview tab of the SQL Editor the drop database button on the toolbar did not work correctly. If pressed the dialog presented did not contain the name of the current database in its message, and generated text such as:
Do you want to drop database `` from DB server ...
Note the empty string where the database name should have been. Further, the text on the dialog button drop was also missing the database name:
The path to the an external
set in the MySQL tab of the
Preferences dialog was ignored by
MySQL Workbench. This prevented the Data Dump
facility in the Admin screen from working correctly because the
required tool could not be found.
The live data editor of the SQL Editor, which was launched by double-clicking a table in the Overview tab, did not behave correctly. If a column value was changed, and the cursor remained in the edited cell, then if the Apply made changes to data source toolbar button was clicked, the contents of the cell reverted to its value prior to editing. However, other cell values that had been edited were correctly saved. (Bug #49301)
In the SQL Editor, when editing live table data, there was no right-click menu item to delete a row. (Bug #49300)
When importing data using the Data Dump tab of the Admin screen, MySQL Workbench did not notify the user of failed imports because it could not detect failed imports. (Bug #49297)
When a export was performed using the Data Dump tab of the Admin screen, and the export failed, the resulting SQL file was not deleted. (Bug #49296)
In the SQL Editor, using the Alter Routine
wizard to generate a script to modify an existing routine in the
live database results in errors, due to incorrect script code
being emitted. For example, the statement
$$ was missing from the start of the script.
When an attempt was made to load the
sakila.sql script file in the SQL Scripts
section of the Model tab, MySQL Workbench crashed with this error:
glibmm-ERROR **: unhandled exception (type std::exception) in signal handler: what: File '/home/kolbe/Downloads/sakila-db/sakila-data.sql' contains invalid UTF-8 data.
In the Overview tab of the SQL Editor, the toolbar buttons to add and drop a schema did not function. Clicking the buttons appeared to have no effect. (Bug #49240)
In the Overview tab of SQL Editor, the toolbar buttons representing large icons, small icons, list, add, and delete did not function correctly. (Bug #49239)
The Configuration tab on the Admin screen
had a text label “Edit my.cnf File”. This text was
not appropriate as on Windows the configuration file is called
In the configuration editor, on the Admin tab, the operation of the Apply and Cancel buttons did not work correctly. If an option was selected, and then Cancel selected in the view changes dialog, and then Apply clicked again, the selected option was incorrectly listed twice in the configuration file. (Bug #49236)
In the Create new server instance wizard, on the MySQL Config File page, clicking the Check path button generated an exception. (Bug #49228)
Even though the server had been stopped, the Server Status graphical panel displayed values for active connections, traffic and key efficiency, giving the impression that the server was still active. (Bug #49225)
The server health graphs Connection Usage and Traffic, in the Server Status panel of Admin tab, appeared to indicate the server was operating at 100% capacity, even when this was not the case.
MySQL Workbench has been changed to use variable scaling, rather than linear scaling, for these graphs. (Bug #49214)
On the Admin screen the labels for the monitoring graphs were difficult to read. Further, the value for Traffic was sometimes displayed as a negative number. (Bug #49211)
In the Log Files tab of the configuration editor, selected from the Admin tab, the option Write Logs to did not work correctly. If either the Files or Tables options were selected from the option list, the MySQL Server would not subsequently start. This was because the options should have been File and Table. (Bug #49123)
When using the Data Dump facility on the Admin screen, the export process appeared to hang when exporting with the Export to Backup Project Folder radio button selected. (Bug #49113)
When using the Create Table wizard in the SQL Editor, the resulting dialog contained certain options that could not be deselected once selected. For example, the Merge Method option featured a list with three options: Prevent Inserts, First Table, Last Table. Note that once one of these options was selected, there was no way to clear this selection, as there was no facility to select anything other than one of these three options. (Bug #49048)
In the General tab of the configuration editor, changing the data directory using the file chooser control led to an invalid directory being introduced into the MySQL configuration file. This prevented the MySQL Server from starting. (Bug #49036)
In the General tab of the configuration
editor in the Admin screen, the option
type provided an incomplete, and incorrectly
capitalized, list of storage engines/table types.
In the Configuration tab of the Admin screen, any changes made and applied were not reflected in the configuration file of a local MySQL Server installation. (Bug #49008)
In the Server Status section of the Admin screen, the values for CPU status appeared to be erroneously multiplied by 100, and the Memory status appeared to be continually 0. (Bug #48994)
In the Document Properties dialog the created date and last changed date values were reversed. (Bug #48104)
When a schema containing tables with foreign key indexes was synchronized with a live server, MySQL Workbench attempted to erroneously drop and recreate at least one of the foreign key indexes. (Bug #47766)
After synchronizing a model with a live database, and saving the resulting modified model, MySQL Workbench crashed. On restarting and attempting to reopen the model file, MySQL Workbench generated this error:
Error unserializing GRT data inserting null value to not null list
In an EER diagram, if relationship links were laid out as desired, and then a synchronization with the live server carried out, the relationship links were repositioned by MySQL Workbench. (Bug #47234)
If a relationship link was selected in the EER Diagram view, and the menu item Plugins, Objects, Copy SQL to Clipboard was selected, an error was generated.
Note that in version 5.2.11 this menu option is correctly disabled for these objects. (Bug #39556)