This section documents all changes and bug fixes applied since the release of 5.2.30.
Functionality Added or Changed
The query execution time was added to the query result status bar. (Bug #53509, Bug #11761054)
Edit, Format, Un/Comment Selection was added. (Bug #55278, Bug #11762657)
MySQL Workbench has been changed so that holding the spacebar while in the EER Diagram view temporarily changes the cursor to the hand tool. When the spacebar is released the cursor reverts to the tool that was selected prior to the spacebar having been pressed. (Bug #52331)
MySQL Workbench would not detect invalid values while they were entered into the properties editor. (Bug #11749933)
These query beautifier problems were corrected:
When the beautifier was used on a query that performed a
join with the
USING keyword, the table
name was concatenated with that keyword.
The beautifier did not recognize the optional
AS keyword in table references. When
AS was used with a table alias, the
beautifier concatenated that keyword and the alias, which
caused any references to the original alias to fail.
Using the beautifier on a query containing
USING resulted in an invalid query being
generated. This was due to missing spaces around
Using the beautifier on a query resulted in an unhandled exception.
If a query was partially selected, and then the beautifier was run, the results were unpredictable. Problems included exceptions, duplicated tokens, and incorrect indentation.
When the beautifier was run on code containing several statements, the code was incorrectly formatted.
A query containing a
CASE keyword was not
The beautifier converted certain tokens to uppercase that should not have been converted.
When attempting to beautify a
INDEX query, the beautifier removed part of the
If a query was written in the SQL Query tab, and then highlighted using the cursor, the beautifier failed with an unhandled exception on calls to beautify, uppercase, or lowercase functions.
Using the beautifier on a
statement resulted in an unhandled exception.
(Bug #58598, Bug #58569, Bug #58347, Bug #58565, Bug #58359, Bug #58367, Bug #58361, Bug #58360, Bug #58357, Bug #58358, Bug #58356)
In the SQL Editor, when entering a hex value into an
INTEGER column, the hex value was
automatically quoted as a string, causing it to be evaluated to
INSERT statements did not include
quote characters for
When exporting a record set using the SQL INSERT statements file format, a number of issues were found:
The first line contained the executed
SELECT statement as a comment but the
LIMIT syntax was located in a new line.
This resulted in the
LIMIT part of the
statement not being commented out.
Strings following the
VALUES keyword were
INSERT statements contained the text
“table” in place of the actual table name.
Existing files were overwritten without prompting the user.
(Bug #58377, Bug #56950)
In the SQL Editor, selecting the default database where the
server contained only a single database had no effect. To avoid
a “No database selected” error, the database had to
be selected in a script using the
A script file that was converted to the
character set was truncated on loading into the SQL Editor.
In the SQL Editor, an out of memory exception occurred when exporting a large record set in the CSV file format. (Bug #55889)
In the SQL Editor, when viewing table data where the number of columns was such that some columns were offscreen, if the End key was pressed to go to the last column in the row, the data grid did not scroll accordingly, so the column containing the cursor was not visible without manually scrolling. (Bug #54753)
Results for queries on rows that contained a null byte (\0) were truncated at the null byte character when displayed in the SQL Editor results pane. (Bug #58099)
In the SQL Editor, it was not possible to create a foreign key relationship between two tables. (Bug #55399)
It was not possible to add a comment for a Layer using the Object Editor. MySQL Workbench has been updated so that it is possible to add a comment for a layer using the Object Editor. (Bug #50668)
In the Model Overview, if a diagram had a title that wrapped to two lines or more, the second line was truncated due to lack of space in the panel. Now MySQL Workbench includes a scrollbar should the diagram titles not fit within the standard panel. (Bug #54952)
MySQL Workbench permitted an
column to be assigned a default value in the Table Editor,
resulting in invalid DDL being generated.
For a column of type
TIMESTAMP, the menu
items Default CURRENT_TIMESTAMP and
Default CURRENT_TIMESTAMP ON UPDATE
CURRENT_TIMESTAMP in the context-sensitive menu of the
Columns tab of the Table Editor were grayed
out. This occurred where a preceding column of type
TIMESTAMP was allocated an explicit default
value. MySQL Workbench should not have prevented setting a value
using the context-sensitive menu for the second defined column
in this case.
Forward engineering a model failed with a duplicate column name
error when the EER diagram contained a view consisting of tables
joined using the
In the Role Editor, the “Drag object from the catalog tree to assign privileges” text label was out of date. The label should have read “Drag objects from Physical Schemata section to assign privileges”. (Bug #56321)
In the Reverse Engineer Database wizard, the ability to select the default schema on the Connection Options page was superfluous. (Bug #56179)
Deleting routine groups from the EER Diagram view did not delete routines. (Bug #56084)
In the Column tab of the Table Editor, it
was possible to set
NULL as the default value
for a column that had been specified as
In the Table Editor, if a data type was selected for a column, this was immediately reflected on the EER Diagram view. However, if the selection was reverted by pressing Control+Z, the EER Diagram was not updated to reflect this, and continued to display the original data type. (Bug #55348)
In the User Defined Data Types Editor, clicking the button to edit the argument list caused the Argument List Editor dialog to be drawn beneath the current dialog. As the dialog with focus could not be accessed, this meant it was not possible to proceed with editing and MySQL Workbench had to be closed. (Bug #55242)
The Modified time displayed in the Model Overview was incorrectly set to the current time. (Bug #55237)
It was not possible to select and copy messages in the Output window of MySQL Workbench. When messages were displayed it was no longer possible to right-click them and select either the Copy Selected Messages to Clipboard or the Clear Output Windows menu items. (Bug #54983)
In the Diagram view switching between tables caused erroneous carriage returns to be added to the DDL code in the Triggers tab. (Bug #54411)
Formatting of view code entered in the View Editor was not retained after synchronization of the model with the server. (Bug #52004)
ENUM values entered into the Inserts Editor
were not automatically quoted.
When objects were double-clicked in the Diagram view, the correct tab was not always switched to in the Object Editor. The Description Editor did however switch to the correct object. (Bug #55994)
Backups dumped to a project folder (file per table) were restored in no particular order. This made it difficult to resume a problematic restore at a specific point. (Bug #56897)
In the Server Access Management tab of the Administrator no user accounts were displayed. Further, attempting to create a new account resulted in an exception. (Bug #57941)
The error message displayed when the mysqldump version needed updating was not informative enough. (Bug #54209)
An error message contained a spelling mistake:
Line 437 of .\backend\wbprivate\workbench\wb_context_ui_home.cpp: std::string msg = strfmt("Error in sercurityManager module: %s",err.what());
Clicking the Configuration tab in the Administrator produced this error:
Error Opening Configuration File Exception: Internal error. File data passed is not in expected format. This is a bug, we would appreciate if you file a bug report at http://bugs.mysql.com.
In the Administrator, attempting to add an account with a login name longer than 16 characters resulted in an exception. (Bug #57300)
When the MySQL service was set to manual in MySQL Workbench, the service was displayed as running in the server status panel, even though the service had not yet been started. (Bug #56919)
In the Connections tab of the Administrator, scrolling did not work correctly with large numbers of connections. (Bug #56144)
When multiple tabs were open in the Administrator, with each connected to a different server, and with export of a database was set up in each, running an export operation resulted in errors. This occurred because MySQL Workbench attempted to export a database selected in a tab other than the currently selected one. (Bug #56113)
In the Configuration tab of the
Administrator it was not possible to enable or disable the
In the Administrator, system health displayed NO DATA. (Bug #52151)
In the Administrator, starting or stopping the monitored server produced this error message:
Could not stop/start server: expected a character buffer object
In the Administrator, monitoring of a remote server did not work. (Bug #58586)
When using the Administrator, the CPU utilization jumped to 50%. (Bug #50578)
If a MWB file was double-clicked to open, but MySQL Workbench was already running, a new instance of MySQL Workbench was launched, rather than opening the file in a new tab in the currently running instance. (Bug #56067)
After printing, the status message displayed included incorrect capitalization. “Print Diagram done” should have been displayed as “Print diagram done”. (Bug #50035)
The menu option View,
item did not appear to have any useful
Autotools were required to be installed locally to build MySQL Workbench from source. (Bug #58263)
The MySQL Workbench tarball contained cached Autotools information. (Bug #58261)
Typing into the Workbench Scripting Shell resulted in an Unexpected Error:
MySQL Workbench has encountered a problem. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
The MySQL configuration file could not be accessed during MySQL Workbench installation. (Bug #56987)
When creating a new server instance, this error occurred when testing the settings:
Operation failed: File doesn't exist
Close tab functionality failed intermittently. This occurred for attempts to close the tab directly or when using the File, Close tab menu item. (Bug #55901)
When setting the data type of a column to
DOUBLE with precision specified, the data
type reverted to
DOUBLE without the desired
precision specifiers. This happened in both the Table Editor and
the SQL Editor.
After the computer woke from the sleep state, MySQL Workbench attempted to reconnect to a connection that had previously been closed in the SQL Editor. (Bug #56302)
In the sidebar of the SQL Editor, when a default schema was selected, other schemas listed in the sidebar were not displayed. (Bug #55864)
The schema editor decreased in size by several pixels each time a new schema was edited. (Bug #49425)
If the Table Editor was resized, it returned to the default size when switching between tables to be edited. (Bug #56314)
In the EER Diagram view, a copied object could not be pasted, if the object had previously been pasted and then edited. (Bug #55336)
The commands to arrange objects were not enabled in the EER Diagram view. This rendered it impossible to move objects to the back or bring them to the front. (Bug #57907)
The SQL Editor did not display the execution times for queries. (Bug #49390)
In the SQL Editor, right-clicking a table name and selecting Alter table did not launch the Alter table dialog as expected. This happened if the table name utilized mixed case letters. (Bug #58223)
In the SQL Editor tab of the Workbench Preferences dialog, if the OK button was not clicked centrally, it was possible to accidentally select or deselect one of the options Treat BINARY/VARBINARY as nonbinary character string or Enable Data Changes Commit Wizard. (Bug #57669)
In the SQL Editor, in the Foreign Key tab of the new-table dialog, it was not possible to select any of the foreign key check boxes. (Bug #56024)
The SQL Editor generated these errors if a query ran longer than 30 seconds:
Error Code: 2013 Lost connection to MySQL server during query Error Code: 2006 MySQL server has gone away
Find and Find and replace did not work in the SQL Query tab. (Bug #56898)
MySQL Workbench crashed when a snippet in the snippet list was right-clicked. (Bug #56588)
Selecting a Refresh or Refresh all button or menu item caused the list of tables and views in the sidebar to become empty. (Bug #55214)
In the Columns tab of the Table Editor, double-clicking to edit or add a new column caused the window to scroll to the top. (Bug #57793)
When saving over a read-only file, MySQL Workbench changed the file permissions to read/write. (Bug #56403)
If the relationship editor was already open, it was not possible to open it for another relationship without closing it first. (Bug #55708)
The forward engineering process generated SQL code that quoted
boolean values, causing incorrect cast values. When a table
contained the logical
BOOLEAN type for a
field it was converted to
expected. However, the values that were supplied for any inserts
were quoted, as in this example:
INSERT INTO mytable (id,flag) VALUES (NULL,'TRUE');
In the Administrator, most columns were not sortable. For example, in the Connections tab, it was not possible to sort connections based on clicking the columns id, User, Host, DB, Command, Time, State, Info. (Bug #55813)
PYTHONPATH environment variable from
other Python installations interfered with MySQL Workbench. At
startup, the error “cannot open SSH Tunnel Manager”
appeared. Further, it was not possible to use the MySQL Workbench
On the Select Object page of the Reverse Engineer Database dialog, the panels displayed when Show Filter was clicked did not resize correctly when Hide Filter was clicked. (Bug #57376)
When an EER diagram that was in the background was closed, it was not possible to reopen it. (Bug #55767)
Creating a many-to-many relationship between two tables resulted in only one index being generated. (Bug #56613)
In the Reverse Engineer SQL Script wizard, on the Input and Options page, the button to select the SQL script file had the text “Brow” instead of “Browse”. (Bug #57929)