This section documents all changes and bug fixes applied since the release of MySQL Workbench 5.0.20.
The undo operation did not completely undo a relationship between two tables. It removed only the line drawn between two tables, but did not undo the fields and keys. (Bug #36645)
Double-clicking a column-heading separator in Find results caused a crash. (Bug #36266)
The scripts generated by the, , and , , include unnecessary SQL code. (Bug #36170)
Themenu item on the context menu of a connection does not have a complementary menu item. The menu has a greyed-out menu item. (Bug #36166)
When a schema used
InnoDB, and then was switched to use
MyISAM, the script generated by Forward Engineer SQL CREATE Script still contained
InnoDB-only syntax. (Bug #35947)
Saving a file restores the column widths of the list view to default under Physical Schemata. (Bug #35718)
When making a column a primary key and this column has
NULLas default value, this default value is not changed. When the table gets synchronized back to the database Workbench creates a statement such as:
ALTER TABLE `test_defhan`.`table1` CHANGE COLUMN `id_table1` `id_table1` INT(11) NOT NULL DEFAULT NULL, ...
This leads to an error:
Error 1067: Invalid default value for 'id_table1' (Bug #32972)