Changes in MySQL Workbench 5.0.27 (2008-11-07)

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

• Functionality Added or Changed

• Bugs Fixed

Functionality Added or Changed

• There was a problem where relationships that were hidden could then not be selected to bring up their relationship editor. Relationships can now be selected as objects in the Layer window. Once selected, the relationship's visible property can be set to True in the Properties window, thus making the relationship visible again. (Bug #40167)

Bugs Fixed

• When a stored routine was edited, the edit cursor jumped back to the start of the page unless typing was constant. (Bug #40426)

• When using the Copy Insert to Clipboard menu item the generated SQL code was incorrect. The “S” was missing from “VALUES” and the data was not included. This resulted in SQL code such as:

  INSERT INTO `table1` (`table1_id`, `descr`) VALUE ();

  (Bug #40041)

• If a trigger was renamed, and the design then synched with a database instance, the generated SQL created a trigger with the new name and then dropped the trigger with the old name. This resulted in this error:

  Error 1235: This version of MySQL doesn't yet support
  'multiple triggers with the same action time and event for one table'

  (Bug #39989)

• The Copy SQL to Clipboard action (right-click menu on table) did not use Windows-compatible line endings. (Bug #39476)

• When a column had a data type BOOLEAN and it was exported using Forward Engineer SQL ALTER, the exported type was BOOLEAN(2) instead of BOOLEAN. (Bug #39257)

• Workbench application performance was poor, with slow loading times and excessive memory usage. (Bug #38439)

• When a DBDesigner model with 333 tables was imported into Workbench the RAM usage went up to approximately 1GB. Workbench then crashed with this exception:

    Error creating cairo context: out of memory

  (Bug #37178)