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.16 (2010-02-17)

Changes in MySQL Workbench 5.2.16 (2010-02-17)

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

Functionality Added or Changed

  • In the SQL editor, the keyboard shortcut to run a single query has been changed to Control+Enter. To run all queries the keyboard shortcut has been changed to Control+Shift+Enter. (Bug #50747)

  • The key sequence Control+Q has been added as a shortcut for the main menu item File, Exit. (Bug #50727)

  • In the SQL Editor a comment has been added to the EDIT statement to clarify its functionality. (Bug #50705)

  • The Manage DB Connections dialog now prevents removal of a connection used by a server instance. (Bug #50547)

  • In the Logs tab of the Administrator it was not possible to view long queries, or copy their text. MySQL Workbench has been changed so that double-clicking an entry in the Logs tab pops up a dialog with the complete text, and also provides a Copy Detail button to copy the text of the entry. (Bug #49442)

  • The data dump facility, used for exporting data to disk, has been modified to enable the --single-transaction option to be specified.

    If --single-transaction is enabled, the table selection will be restricted the following ways:

    • If a single schema is selected, it is possible to select/deselect its tables as required.

    • If more than one schema is selected, all tables from these schemas must be selected because mysqldump --databases will be used in this case.

    (Bug #49220)

  • When a model with multiple EER Diagrams was opened, all EER Diagrams would be displayed in tabs. This happened whether or not a EER Diagram had been displayed in a tab prior to saving the model.

    MySQL Workbench has been changed so that the EER Diagram tab state is saved, so that when a model is opened, only those EER Diagram tabs that were open on save are restored. This prevents unnecessary cluttering of the interface. (Bug #44454, Bug #50732)

Bugs Fixed

  • Security Fix: Passwords were stored in plain text format in the file server_instances.xml.

    To improve security MySQL Workbench has been changed in the following ways:

    • The password is no longer stored in the connection XML file.

    • When a connection is opened, a password request dialog is displayed and the password requested. The password can optionally be stored in the system keychain/vault/keyring.

    • When editing a connection profile, you can also store the password in the system keychain.

    • For compatibility, when MySQL Workbench starts it will look for passwords stored in the XML file. If any password is found, it will be removed from the XML file and automatically stored in the keychain. When MySQL Workbench exits, the connections file will be free from passwords.

    (Bug #50194)

  • When using the Server Administration link, or Manage Security link, on the Home screen, to log in to a remote server through an SSH connection, if the password dialog was closed, and cancellation of the SSH connection dialog acknowledged, this exception was generated:

    Exception = System.Runtime.InteropServices.SEHException
    Message = External component has thrown an exception.
    FullText = System.Runtime.InteropServices.SEHException: External component has thrown an
       at MySQL.Forms.DrawBoxImpl.drawbox_mouse_click(Object sender, MouseEventArgs e)

    (Bug #51088)

  • In the Create a new server instance wizard, on the last page of the wizard if the Back button was pressed and then the Next button pressed, an error was generated stating the server instance already existed. (Bug #51060)

  • Using File, Export, Forward Engineer ALTER Script to export a model resulted in MySQL Workbench generating the exception AccessViolationException. (Bug #51053)

  • In the SQL Editor, if using the Alter Table dialog, attempting to apply changes after renaming an index resulted in this error:

    SQL Error 1091: Can't DROP 'username_foo'; check that column/key exists

    (Bug #50970)

  • In the System Profile tab of the Manage Server Instances dialog, if the Path to configuration file textfield was set using the browse button, ..., the value in the textfield appeared to be set correctly to the selected file. However, if the dialog was closed and reopened, the new path was not displayed in the text field. If the path was manually entered, rather than using the browse button, the textfield would display the correct path even if the dialog was closed and reopened. (Bug #50965)

  • In the SQL Editor, if the Edit Data dialog was invoked for a table, and some data edited, MySQL Workbench crashed when the Apply SQL button was clicked. (Bug #50920)

  • An exported script containing triggers and views resulted in the error #1046 - No database selected when run on the MySQL Server. This was due to a missing USE DATABASE statement in the generated script. (Bug #50900)

  • The second invocation of File, Print caused MySQL Workbench to crash. (Bug #50885)

  • The SQL code editors used in the modeling functionality within MySQL Workbench, for example in the Triggers tab of the Table Editor, failed to identify and highlight SQL code errors. (Bug #50835)

  • In the SQL Editor the text Parsing SQL ... displayed in the status bar remained once the parsing was complete.

    MySQL Workbench has been changed to display No errors found once parsing has successfully completed. (Bug #50833)

  • If a MySQL server was set to accept named pipe connections only, and then a server instance created in MySQL Workbench using a named pipe connection, it was not possible to subsequently connect to the server with MySQL Workbench. (Bug #50830)

  • Expanded Schemata Palettes in the SQL Editor would collapse when switching between SQL Editor tabs. (Bug #50815)

  • In the SQL Editor the toolbar button to execute SQL statements was missing.

    MySQL Workbench also now includes a new toolbar button to execute a single statement. (Bug #50791)

  • In the MySQL Model tab, if the Table Editor was launched and then the Home screen tab clicked, MySQL Workbench displayed the MySQL Workbench Unexpected Error dialog. (Bug #50768)

  • On the MySQL Model page using Roles and Users to grant privileges to a schema resulted in errors when the model was forward engineered, and the resulting script applied against a MySQL server. The script failed due to invalid SQL syntax because the SQL created did not correctly apply the privileges to all schema objects. (Bug #50762)

  • In the Data Dump facility of the Administrator, attempting to export a schema to disk failed if a table name contained a space. (Bug #50728)

  • In the Workbench Scripting Shell dialog, clicking an item in the value inspector panel (lower left corner) caused an exception:

    System.Runtime.InteropServices.SEHException: External component has thrown an
       at MySQL.Grt.TreeModel.expand_node(NodeId node)
       at MySQL.Grt.GrtTreeModel.TreeViewExpanding(Object sender, TreeViewAdvEventArgs e)
       at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
       at Aga.Controls.Tree.TreeViewAdv.OnExpanding(TreeNodeAdv node)

    (Bug #50683)

  • In the Data Dump facility of the Administrator it was not possible to import a file where the path contained a space. (Bug #50609, Bug #50007)

  • In the SQL Editor a situation occurred where all results tabs could not be closed. Further, results tabs were incorrectly created with the same label. (Bug #50334, Bug #50865)

  • In the Manage DB Connections dialog it was not possible to select a default schema for the Socket/Pipe connection type because this facility was not provided by the dialog user interface. (Bug #50283)

  • It was possible to connect to a database using a password containing a space. However, when this connection was used to attempt a backup the operation failed, due to the password not being correctly quoted. (Bug #50213)

  • The messages generated by mysqldump when a data export operation failed were difficult to interpret, for example:

    Operation failed with exitcode 2

    (Bug #50137)

  • In the SQL Editor, when editing table data, if an operation failed when changes were applied, the error message was not clearly visible. (Bug #50112)

  • In the SQL Editor, if a LONGTEXT field was being edited in the table data live editor, when the changes were applied an error was generated.

    MySQL Workbench has also been changed so that large text values need to be edited in an external editor and then pasted into the grid cell. (Bug #50111, Bug #50692, Bug #50948, Bug #50814)

  • When synchronizing a schema with a live server, the scale of columns with type DECIMAL was erroneously set to zero. For example, a DECIMAL(17,5) was found to be set to DECIMAL (17,0) in the generated script. (Bug #50110)

  • When a non-SSH server instance was created, and a connection made to a remote server, only the Data Dump facility of the Administrator was available. The same problem occurred if SSH-based administration was deselected for the server instance. (Bug #50098)

  • In the SQL Editor, if a database was selected in the Overview tab and then either the Drop Schema... context menu item was selected, or the drop schema toolbar button clicked, the DROP DATABASE dialog was displayed. However, if the dialog close button was then clicked to cancel the dialog, the database was still dropped, instead of being unaffected by the cancelling of the dialog. (Bug #50072, Bug #50960)

  • In the Create a new server instance wizard, if an operating system of type Windows (MySQL 5.1 Installer Package) was selected, this error was generated on the Test Settings page:

    Error: File C:\Program Files\MySQL\MySQL Server 5.1\my.ini doesn't exist

    This was because the file was actually stored in C:\Programas\MySQL\MySQL Server 5.1\my.ini.

    Similar bugs where the configuration file could not be found were reported on both English and non-English systems. (Bug #50050, Bug #50635, Bug #50966, Bug #50873, Bug #51008)

  • If a table was dropped from a live database, and then the model synchronized, the dropped table would be detected, but the table was not dropped from the model concerned. (Bug #50000)

  • For a default MySQL Server installation, no my.ini or my.cnf file is created. This proved problematic when creating a server instance in MySQL Workbench because the Create a new server instance wizard expected a configuration file to be specified. If the path to the configuration file was left blank, a model error dialog was displayed by the wizard. If alternatively, one of the standard locations for the configuration file was entered, problems arose when an attempt was made to subsequently change configuration values in the configuration section of the Admin screen. The problems included MySQL Workbench hanging, and repetitive requests for a 'super user' password. (Bug #49766, Bug #50317)

  • In the SQL Editor, in the add routine dialog, if the template was used, and a simple SELECT 1; statement added to the template, this error was generated when changes were applied:

    ERROR 1064: You have an error in your SQL syntax; check the manual that
    corresponds to your MySQL server version for the right syntax to use
    near '' at line 3
    SQL Statement:
    CREATE PROCEDURE `world`.`new_routine` ()
    SELECT 1

    (Bug #49710)

  • In the Forward Engineer SQL Script wizard, selecting the check box Omit Schema Qualifier in Object Names caused the CREATE SCHEMA statement to be removed. DROP SCHEMA statements were also removed, even if the Generate DROP SCHEMA check box was selected.

    MySQL Workbench has been changed so that if the Omit Schema Qualifier in Object Names check box is selected, it is possible to optionally select the check box Insert USE Statements, to enable or disable the use of USE statements. (Bug #49682)

  • If the Data Dump facility in Administrator was used to export to a self-contained file, then when that file was imported an unhandled exception was generated. (Bug #49529)

  • If the MySQL Server was stopped then attempting to access the Logs, Accounts, Connections, Variables or Data Dump tabs in the Administrator resulted in unhandled exceptions. (Bug #49439)

  • MySQL Workbench did not support SSH keys that required a passphrase to be entered. (Bug #49418)

  • When using an SSH connection to manage a remote server, MySQL Workbench repeatedly prompted the user to enter a password, even though a key file had been specified. (Bug #49307)

  • In the SQL Editor, when using the live editor, if Query, Export Results was selected from the main menu and a CSV output format chosen, the exported data was found to be in tab delimited format, rather than CSV format. (Bug #49303)

  • When MySQL Workbench was connected to a remote server using an SSH connection, and a data export operation performed, MySQL Workbench actually attempted to perform the data export on a local server instance, rather than on the connected remote server. If the remote and local server had a common user account, a backup could be performed that appeared to complete successfully, but which contained data from the local server rather than the connected remote server. (Bug #49295)

  • In the Alter Table dialog of the SQL Editor, support for triggers appeared to be provided, but underlying functionality was missing. (Bug #49287)

  • In the SQL Editor, if Alter Table was invoked, and the collation for a column changed, no changes were detected after clicking Apply. (Bug #49277)

  • The descriptions used for options in the Advanced Options tab in the Data Dump section of the administrator were lacking clarity and in some cases dated. (Bug #49224)

  • The import log contained messages with redundant parentheses. (Bug #49218)

  • There was no facility to cancel the Export to Disk process, once started, in the Administrator. Further, the Start Export button erroneously remained enabled during the export process, enabling the user to start new export processes, resulting in errors. (Bug #49115)

  • In the Data Dump facility of the Administrator, if a schema was selected, but its corresponding check box not selected, and then several of its tables selected for export, this error occurred when the Start Export button was clicked:

    Nothing to do, no schemas or tables selected.

    (Bug #49110)

  • In the Create a new server instance wizard, using the default SSH Key Path, ~/.ssh/id_rsa, resulted in a 'file not found' error when testing the connection. However, if the path was entered as /home/username/.ssh/id_rsa the connection test was successful. The same problem was also present in the Manage DB Connections dialog. (Bug #49090)

  • The first connection created with New Connection did not appear immediately in the list of available connections. (Bug #49079, Bug #49801)

  • Numerous variables were missing from the DDL section of the Status Variables tab in the administrator. (Bug #49073, Bug #49077)

  • In the configuration file editor it was possible to select a directory, such as Temp directory on the General tab, without specifying a corresponding path. (Bug #49035)

  • In the General tab of the configuration file editor, the option Default table type was present, even though it was deprecated in MySQL Server 5.0. Further, selecting this option and applying changes did not change the server configuration file. (Bug #49006)

  • If the command for checking server status was changed in a server instance, the change did not take effect unless MySQL Workbench was restarted. (Bug #48992)

  • MySQL Workbench did not correctly detect the status of MySQL Servers where multiple servers were running on the same host, and so displayed incorrect server status on the Admin screen. (Bug #48975)

  • In the Forward Engineer SQL Script wizard, selection of the Skip Creation of FOREIGN KEYS check box was not reflected in the generated script. (Bug #47969)

  • When using MySQL Workbench to create an ALTER script, the generated script did not reflect columns where only the case of the column name had changed. (Bug #45556)

  • If a schema that contained tables with no engine defined was reverse engineered, and then the engine type was changed in MySQL Workbench, then when the model was exported the ALTER script did not contain code to change the engine of the table. (Bug #45110)