Skip navigation links
MySQL Workbench :: A MySQL Workbench Change History :: A.2 Changes in Release 5.1 :: A.2.5 Changes in MySQL Workbench 5.1.15 (26th June 2009 beta)
A.2.6 Changes in MySQL Workbench 5.1.14 (19th June 2009 beta) »
Section Navigation      [Toggle]

A.2.5. Changes in MySQL Workbench 5.1.15 (26th June 2009 beta)

This section documents all changes and bug fixes that have been applied since the release of 5.1.14. This release is RC3.

Functionality added or changed:

  • A routine object was deleted if its code was removed from the routine group. This behavior has now been noted in the main documentation. (Bug#45738)

Bugs fixed:

  • Selecting Database, Generate Catalog Diff Report from the main menu caused MySQL Workbench to crash. (Bug#45652)

  • Generated INSERT statements did not have a database name.

    The generated INSERT statements were at the end of the SQL output. However, there was no USE database statement before the group of inserts. The comment before the group of INSERTS did refer to the database table.

    If you had multiple databases, this generated errors on import. (Bug#45642)

  • In the Forward Engineer SQL Script wizard, when the Show Filter button was clicked, the left hand panel containing database and table names was too narrow, especially if a long database name or table name was used. This made it hard to determine which tables to select. (Bug#45623)

  • The File, Export, Forward Engineer SQL CREATE Script wizard contained malfunctioning buttons. When prompted with the message “Do you want to overwrite an existing .sql file?”, the Replace and Cancel buttons had the reverse effect. Clicking Replace cancelled the action, whereas clicking Cancel proceeded to the next step. (Bug#45619)

  • In Ubuntu Linux right-clicking on any item in the Catalog, Layers, User Types, or History tabs, or other tabs typically docked in the right hand side of MySQL Workbench, did not display a context-sensitive menu. (Bug#44298)

  • MySQL Workbench Syncronize Model feature had unexpected behavior. For example, synchronizing the model with the live database would cause changes to the database, even if this was not desired. Also, if tables were dropped in the live database, and the model synchronized, the changes to the live database were not reflected in the model. Further, if a model was created and synchronized to an empty schema in the live database, when synchronization took place again, MySQL Workbench would indicate many changes were required, even if no changes had been made to the model or database. (Bug#42149)

  • Double-clicking a layer in the Layers tab did not select it in the EER Diagram canvas. However, other objects in the Layers tab could be selected on the EER Diagram canvas in this manner. (Bug#34938)

  • Right-clicking on a relationship in the EER Diagram canvas, and selecting Edit in New Window... from the context-sensitive menu, had no effect. (Bug#34069)