MySQL Workbench Release Notes  /  Changes in MySQL Workbench 5.0  /  Changes in MySQL Workbench 5.0.30 (2009-02-18)

Changes in MySQL Workbench 5.0.30 (2009-02-18)

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

Bugs Fixed

  • MySQL Workbench crashed when the mouse wheel was used. If you scrolled the Options tab of the Table Editor, closed the Table Editor and then used the mouse wheel again on the MySQL Model page, MySQL Workbench crashed. (Bug #42847)

  • Introducing a UserType into a model caused the File, Export, Forward Engineer SQL CREATE Script wizard to crash. Further, performing a Plugins, Objects, Copy SQL to Clipboard operation also caused MySQL Workbench to crash. (Bug #42085)

  • The Forward Engineer SQL CREATE Script wizard failed to generate a script correctly.

    This happened when using the File, Export, Forward Engineer SQL CREATE Script facility. If, in the wizard, Object of type MySQL table was selected, and then all tables added to the Exclusion Masks pane, before moving back the required table to the Objects to Process pane, the script was generated for the entire database rather than the selected table. (Bug #41475)

  • When a diagram was renamed, the history displayed:

    Rename 'new name' to 'new name

    It should have instead displayed:

    Rename 'old name' to 'new name'

    (Bug #41355)

  • If a model contained a View that was using a Function, and an attempt was made to Synchronize the database, an error was generated such as:

    Error 1305: FUNCTION `bleble` does not exist

    A similar error was also generated if the Forward Engineer SQL CREATE Script wizard was used. (Bug #40846)

  • The viewport, which is the combobox in the top right corner of Workbench, did not scale to less than 40%. However, resizes above 40% worked fine. (Bug #39607)

  • The Forward Engineer SQL ALTER Script wizard produced an erroneous script.

    If Forward Engineer SQL CREATE Script was used to generate a script and this was then used as an input to Forward Engineer SQL ALTER Script, without having made any changes to the model, then an ALTER script with no changes should be produced. However, the ALTER script showed many changes, even though no changes had been made to the model. (Bug #37709)