MySQL Workbench Release Notes  /  Changes in MySQL Workbench 5.0  /  Changes in MySQL Workbench 5.0.21 (2008-04-27)

Changes in MySQL Workbench 5.0.21 (2008-04-27)

This section documents all changes and bug fixes applied since the release of MySQL Workbench 5.0.20.

Bugs Fixed

  • 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 File, Export, Forward Engineer SQL ALTER Script and File, Export, Forward Engineer SQL CREATE Script include unnecessary SQL code. (Bug #36170)

  • The Copy Connection nn menu item on the context menu of a connection does not have a complementary Paste Connection menu item. The Edit menu has a greyed-out Paste Connection 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)

  • Forward Engineer wizard failed to create a table, but did not show any error messages. (Bug #35874)

  • 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 NULL as 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

    This leads to an error:

    Error 1067: Invalid default value for 'id_table1' (Bug #32972)