An open model that has not been saved is now automatically saved after a user-settable period. On loading a model file, MySQL Workbench will notify the user if the file was not previously saved correctly, due to a crash or power failure. MySQL Workbench can then attempt to recover the last auto-saved version. Note that for automatic recovery to be available for a new file, it will have to have been saved by the user at least once. (Bug #56718)

The Autosave feature was added. (Bug #50044, Bug #11757926)

Security Fix: A security bug was fixed. (Bug #57080)

Clicking the Inserts tab of the Table Editor resulted in the MySQL Workbench Unexpected Error dialog being displayed. (Bug #57346)

If an EER diagram was created and then closed, attempting to reopen it caused MySQL Workbench to display an unexpected error dialog. (Bug #57259)

In the Model View, MySQL Workbench crashed when the Output tab was reopened after previously being closed. (Bug #57150)

Attempting to open the Table Editor in the SQL Editor multiple times for a table that contained no primary key caused MySQL Workbench to crash. (Bug #57139)

Changes made to a server instance were not saved. In particular, changing installation type to “Custom” was not saved, and changes to the sudo command were also not saved. (Bug #57026)

When attempting to open an EER Diagram by double-clicking it in the Model Overview, MySQL Workbench generated this unexpected error:

Cannot access a disposed object.
Object Name: ModelDiagramForm.

(Bug #56963)

When synchronizing a model to a live database, if a database was deselected in the wizard, a DROP statement for that database was generated in the SQL code to prevent it from being part of the synchronization process. This caused that database to be dropped from the live database, with corresponding loss of all data. (Bug #56938)

In the Alter Table dialog of the SQL Editor, attempting to create a new index in the Index tab was not actioned when the Apply button was clicked. The dialog reported that “no changes to object were detected”. (Bug #56906)

It was only possible to connect to a MySQL server for administration using an SSH connection. (Bug #56874)

Scripts could successfully be executed on the MySQL Server failed to execute in the MySQL Workbench SQL Editor. (Bug #56833)

If a table containing a User Defined Type based on VARCHAR was forward engineered, the resulting SQL did not correctly quote the VARCHAR value, resulting in a server error. For example, this code was generated:

CREATE  TABLE IF NOT EXISTS `x`.`tabley` (`customstring` VARCHAR(10));
INSERT INTO `x`.`tabley` (`id_customstring`) VALUES (example);

The correct INSERT statement should be:

INSERT INTO `x`.`tabley` (`id_customstring`) VALUES ('example');

(Bug #56710)

In the Administrator, clicking the Data Dump tab generated the error Error updating DB: float division and schemata were not displayed. (Bug #56658)

In the SQL Editor, if some table data was edited, and then the connection to the server was lost, clicking the Apply changes to data toolbar button caused MySQL Workbench to crash.

Now MySQL Workbench shows an error message in the Output tab when a connection is lost. Once the connection is back up, clicking Apply changes to data re-establishes the connection and sends the changes to the server. (Bug #56170)

Screen areas in the Administrator did not redraw correctly. It was necessary to move the main window to force a redraw. (Bug #55490)

Folding of iteration statement blocks, such as WHILE, REPEAT, and LOOP, did not work correctly in the SQL Editor. The loop end constructs such as END WHILE, END REPEAT, and END LOOP were not recognized as expected. (Bug #55358)

If a foreign key was set to RESTRICT for On Delete and On Update on the Foreign Keys tab of the Table Editor, MySQL Workbench generated SQL code to drop and add this key on every subsequent synchronization attempt. (Bug #55155)