If MySQL Workbench attempts to connect to MySQL Server version 4.x, an error message is generated to indicate this version is not supported. (Bug#51455)

A description column has been added to the snippets table. (Bug#51010)

Various improvements to the SQL Editor user interface, including additional context-sensitive menu items in the Object Explorer, additional buttons in the Create Table and Alter Table dialogs, and more clearly displayed error messages. (Bug#50637, Bug#49918)

In the SQL Editor, the Comments tab in the Create View dialog has been removed. (Bug#49270)

The Output window only appeared in the Model context. MySQL Workbench has been changed so that the Output window now has its own tab on the main screen. (Bug#48988)

In the SQL Editor, the wrong table was displayed when using EDIT. This happened if two schemata contained tables with the same name. For example, if two schemata, schema1 and schema2 both contained a table t1, then if the following SQL was entered and executed, schema2.t1 would be displayed instead of schema1.t1:

use schema1;
edit t1;

(Bug#52401)

MySQL Workbench crashed when synchronizing a model to a live server. (Bug#51892)

MySQL Workbench crashed while attempting to edit code in the SQL Editor. (Bug#51815)

The New Server Instance wizard did not set the correct name for the startup script, when the installation type was set to Fedora Linux (Vendor Package). Testing the connection resulted in the error “Operation failed: /etc/init.d/mysql start is invalid”. (Bug#51802)

In the Object Explorer of the SQL Editor, right-clicking on a table displayed the menu option Send to SQL Edtor. Editor was spelled incorrectly. (Bug#51790)

When synchronizing a model containing a large number of Stored Routines, not all routines were synchronized with the live server. (Bug#51731)

When synchronizing between two triggers, unexpected USE statements and the comment “-- Trigger DDL Statements” appeared intermittently. This caused a syntax error in the script. (Bug#51728)

If a connection was opened for querying and then Ctrl+W quickly pressed to close the connection, MySQL Workbench would crash. (Bug#51685)

When opening the ip2nation.sql file MySQL Workbench crashed. (Bug#51606, Bug#51531)

Exporting a result set to a CSV file resulted in a file with a trailing comma appended to each line including the heading. (Bug#51594)

In the Inserts tab of the Table Editor, if a row was right-clicked and Delete selected rows selected, MySQL Workbench crashed. (Bug#51584)

MySQL Workbench crashed if objects were sequentially selected in the EER Diagram view. (Bug#51573)

In the Alter Table dialog of the SQL Editor, when a table was edited and changes applied, if subsequent changes were made and applied an error would result, as MySQL Workbench attempted to use ADD COLUMN rather than CHANGE COLUMN. (Bug#51481)

When Manage Import / Export was clicked on the Home screen, a server instance selected, and then OK clicked, MySQL Workbench displayed an error dialog with the following message:

MySQL Workbench has encountered a problem, External component has thrown an
exception.

(Bug#51477, Bug#51665, Bug#51703, Bug#51733, Bug#51800, Bug#51870, Bug#51895, Bug#51963, Bug#51944, Bug#51999, Bug#52052, Bug#52262)

Building MySQL Workbench from source failed if LDFLAGS="-Wl,--as-needed" option was specified. (Bug#51469)

When a model with a view was exported using File, Export, Forward Engineer SQL CREATE Script, a semi-colon was added to the end of the CREATE VIEW statement, even if one was already present from the view code entered. (Bug#51416)

On the MySQL Model tab, if a table was clicked on and edited using the context menu option Edit Table, MySQL Workbench crashed. (Bug#51410, Bug#50936)

If all screens and tabs were closed in MySQL Workbench and then Data, Manage Connections selected, then when the Manage DB Connections dialog was closed an unknown exception occurred. (Bug#51403)

If a server instance was created with the New Instance wizard with SSH disabled, then the following exception occurred when attempting to administer the server instance:

Exception = System.Runtime.InteropServices.SEHException
Message = External component has thrown an exception.
FullText = System.Runtime.InteropServices.SEHException: External component has thrown an
exception.
   at MySQL.Forms.DrawBoxImpl.drawbox_mouse_click(Object sender, MouseEventArgs e)
   at System.Windows.Forms.Control.OnMouseClick(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32
clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam,
IntPtr lparam)

(Bug#51368, Bug#51476, Bug#51522, Bug#51483, Bug#51978, Bug#51810, Bug#51883, Bug#51803, Bug#52115, Bug#52163, Bug#51292, Bug#51668, Bug#51784, Bug#51789, Bug#51940, Bug#51947, Bug#52021, Bug#52028, Bug#52108, Bug#52240)

After exporting a schema to disk, importing the schema did not restore the tables. (Bug#51261)

In the Routine Editor, the editor added “//” as the last delimiter, even though “DELIMITER $$” was used at the beginning of the code. (Bug#51247)

In the SQL Editor, if a foreign key name was changed using the Foreign Key tab or Indexes tab of the Alter Table dialog, the following error was generated:

Type mismatch: expected type string, but got list

(Bug#51192)

When the MySQL Workbench source code was configured, the package gnome-keyring-1 was not found. (Bug#51090)

There were discrepancies between the list of pre-requisite packages given on the MySQL Workbench website and those listed in the README file in the MySQL Workbench distribution. (Bug#51085)

In the Administrator section of MySQL Workbench, if a new user was created, the password was not correctly applied for the account, resulting in the new user being denied access when an attempt was made to connect to a server with that user account. (Bug#50983, Bug#51464)

An Out of Range exception occurred when switching from the Table Editor to the Home screen. (Bug#50980, Bug#51030)

MySQL Workbench reported a server as not running, even though the server was correctly running. MySQL Server concerned was running on Windows 7, 64-bit. (Bug#50585)

When using the main menu item Scripting, Run Workbench Script File, the dialog appended “.lua” to the selected filename. This resulted in a failure to load the desired file. (Bug#50501)

In the SQL Editor, field names containing an underscore were displayed incorrectly on the Results tab. Instead of the underscore being displayed in the correct location the following character appeared underlined. (Bug#50132)

When a schema with Foreign keys and associated automatically generated foreign indexes was exported with the Skip Creation of FOREIGN KEYS checkbox selected, the generated script still contained the indexes. (Bug#49987)

In the SQL Editor, in a result set tab it was not possible to copy values from the result set.

MySQL Workbench has been changed to include the context sensitive menu items Copy row values and Copy field content. (Bug#49683, Bug#50170)

The live data editor in SQL Editor did not allow the columns to be sorted in descending order by clicking the column heading. It only allowed column sorting in ascending order through clicking the column heading. (Bug#49302)

In the Overview tab of the SQL Editor there was no scrolling facility available. This meant that if the model contained a large number of schema objects the panel area was quickly filled, and it was not possible to view all of the objects without the ability to scroll. (Bug#49290, Bug#51634)

In the SQL editor, if Alter Table was invoked for a table, and then the partitioning tab selected and partitioning enabled, it was possible to select a partition count of 0, which then generated an error if an attempt was made to apply changes. (Bug#49050)

In the Overview tab of the SQL Editor, if there were a large number of schemata, it was not possible to access certain schemata, as they did not all fit on the schema tab control.

MySQL Workbench has been changed so that there is now a small drop down control that allows you to select the required schema, even if it is not currently visible on the schema tab control. (Bug#48898, Bug#50169)

When using the option Omit Schemata Qualifier in Object Names in the Forward Engineer dialog, the schema name still appeared in DROP, CREATE SCHEMA, INSERT and USE statements. The schema name also appeared in the table comments. (Bug#46837, Bug#51411)