Documentation Home
MySQL Workbench Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 1.0Mb
PDF (A4) - 1.0Mb

MySQL Workbench Release Notes  /  Changes in MySQL Workbench 5.2  /  Changes in MySQL Workbench 5.2.30 (2010-11-20)

Changes in MySQL Workbench 5.2.30 (2010-11-20)

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

Functionality Added or Changed

  • An advanced search and replace dialog has been added to MySQL Workbench. This can be accessed from the main menu Edit option, Find and replace or the keyboard shortcut Control+Shift+f. (Bug #56629)

  • MySQL Workbench has been changed so that the Query Editor in the SQL editor includes an SQL formatter. Code can be highlighted and formatted using the Edit, Format menu item. (Bug #50822)

Bugs Fixed

  • The default settings for the Export Directory Path in the Workbench Preferences dialog used mixed file path delimiters (both '/' and '\'). (Bug #57944)

  • When importing an SQL script using the Reverse Engineer SQL Script wizard, copying a path from the clipboard to the Select SQL script file input box resulted in an invalid path error. (Bug #57927)

  • For attempts to connect to a server using SSH, MySQL Workbench produced this error message after the user entered the password:

    AttributeError: ServerProfile instance has no attribute 'serverInfo'

    (Bug #57695)

  • The implementation of get_local_ip_list() had several problems:

    • It did not have a graceful fallback state in the event of errors.

    • It failed if ifconfig was not on the default user path.

    • It did not handle IPv6 addresses.

    (Bug #57537)

  • When a foreign key was created manually, if the referenced table did not exist, MySQL Workbench crashed. (Bug #57470)

  • In the EER diagram view, the table titles were the same color as the background color, making the table titles illegible. (Bug #57428)

  • After a query was executed, MySQL Workbench crashed when the Export button was clicked to export the result set to a file. (Bug #57379)

  • When a model was forward engineered with File, Export, Forward Engineer SQL CREATE Script, the generated script contained a statement that consisted of a single delimiter, ';'. (Bug #57378)

  • In the SQL Editor, it was not possible to close the last remaining tab. Closing the last remaining tab should result in a new blank tab being displayed. (Bug #57137)

  • If the SSL option was selected for a standard TCP/IP connection, there was no facility provided to enter the SSL certificate details. (Bug #57101)

  • On Linux Fedora 14, MySQL Workbench produced this error at startup:

    /usr/bin/mysql-workbench-bin: error while loading shared libraries:
    cannot open shared object file: No such file or directory

    (Bug #56863)

  • It was not possible to change the name of an EER Diagram. The facility was missing from the Diagram Properties and Size dialog. (Bug #56625)

  • The safe updates option on the SQL Editor tab of the Preferences dialog required a MySQL Workbench restart to take effect. (Bug #56159)

  • In the Table Editor of the SQL Editor, on the Foreign Keys tab, selecting the Referenced Table dropdown for a database containing a large number of tables caused MySQL Workbench to become unresponsive while the dropdown was being populated. (Bug #56014)

  • In the Create Table dialog of the SQL Editor, if a new column was created with a synonym data type such as INTEGER, the datatype would appear blank, both in the interface and in the generated SQL. This resulted in an error when clicking the Apply SQL button. (Bug #55620)

  • Foreign keys were not updated when a referenced column was deleted. (Bug #55219)

  • The output generated as a result of using the Print and Print Preview menu items was incorrect. Only the magnified top left corner of the EER diagram was displayed. (Bug #55139)

  • In the Alter Table dialog of the SQL Editor, attempts to reorder columns failed. If a column position was changed, and then the Apply button was clicked, the dialog reported that no changes to the object were detected. (Bug #54923)

  • When a new instance was created to connect using SSH with an SSH certificate file, the location of the certificate file was not saved. (Bug #52048)

  • In SQL Editor, when using the Alter Table facility to set a column to Auto Increment (AI), the dialog reported that No changes to object were detected. (Bug #50214)