MySQL Workbench Release Notes  /  Changes in MySQL Workbench 5.1  /  Changes in MySQL Workbench 5.1.10 (2009-04-10)

Changes in MySQL Workbench 5.1.10 (2009-04-10)

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

Bugs Fixed

  • It was not possible to edit the cardinality of existing relations using the MAC OS X version of MySQL Workbench. Attempting to change the cardinality using the radio buttons had no effect. For example, it was not possible to change a relation from one-to-many to one-to-one. (Bug #44043)

  • When a nonstandard port was specified in Database, Forward Engineer..., such as 3307, MySQL Workbench still attempted to connect to port 3306. (Bug #44014)

  • When a foreign key was created, a column was selected in the original table, but no column was selected in the foreign table. If the project was saved and an attempt was made to reload it, this error message was generated:

    Unserializing GRT data - Inserting null value to not null list

    This error prevented MySQL Workbench from opening the project file, resulting in all model data being inaccessible. (Bug #43997)

  • The name of the table displayed on the tab in the Table Editor did not update when the table name was changed in the editor. (Bug #43960)

  • Data entered using the Inserts tab in the Table Editor was not displayed in the Inserts tab, but was saved to the MWB file when the project was saved. The data could be viewed in MySQL Workbench running on platforms other than OS X, but the OS X version of MySQL Workbench did not display the data entered using the Inserts tab. (Bug #43907)

  • When a plugin was installed using the Tools, Install Plugin/Module File... menu option, MySQL Workbench copied the selected plugin and reported:

    'Copied module /Users/tilman/Desktop/SymfonyYmlExport.grt.lua to
    '/Users/tilman/Library/Application Support/MySQL/Workbench/modules/SymfonyYmlExport.grt.lua'
    Please restart Workbench for the change to take effect.'

    When restarted, MySQL Workbench crashed. MySQL Workbench could only be fully restarted by first removing the installed file from the modules directory. (Bug #43906)

  • Soon after MySQL Workbench was launched, error popup dialogs were generated with this message:

    "AXDocument" attribute unsupported by <some component>

    This occurred on the OS X version of MySQL Workbench, when a third-party usage monitoring utility was running. This error was due to the fact that custom exception reporting was disabled by default. (Bug #43872)

  • An attempt to edit a table resulted in this error:

    The plugin db.mysql.editors.mwbplugin does not
      contain the published object DbMysqlTableEditor

    This only happened if the project was opened immediately after MySQL Workbench was started. (Bug #43863)

  • If a MySQL Workbench project file was opened, all tabs closed, and then File, New selected, MySQL Workbench crashed with this error message:

    Unknown exception caught in c:\users\tax\documents\visual studio 2008\projects\wb
    5.1\workbench\backend\windows\wbprivate.wr\src\Wb.h at line 994.

    (Bug #43850)

  • If an attempt was made to use the undo feature after having first saved a project, MySQL Workbench crashed. (Bug #43849)

  • When creating a new 1:n link MySQL Workbench froze. (Bug #43812)

  • Using the Navigator to zoom in and out of an EER diagram view caused MySQL Workbench to crash. (Bug #43782)

  • The Many-to-Many Table generated by MySQL Workbench was of engine type Server Default. It should have been of type InnoDB. (Bug #43776)

  • On opening a diagram the file tables layout was broken. All tables were placed in the top left corner.

    It appeared that MySQL Workbench stored the diagram layout in the MWB file correctly but it was not retrieved correctly on file load. (Bug #43455)

  • In the EER Diagram view, if the Tables folder was expanded in the Catalog Palette, and then a table dragged onto the EER Diagram, the expanded Tables folder immediately collapsed. (Bug #41922)