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.18 (2010-04-13)

Changes in MySQL Workbench 5.2.18 (2010-04-13)

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

Functionality Added or Changed

  • MySQL Workbench now features the ability to copy field data in the SQL Editor results tab in quoted or unquoted mode. (Bug #51041)

Bugs Fixed

  • When using the Forward Engineer SQL Script wizard, the wizard did not terminate DROP procedure IF EXISTS statements with a semicolon. This caused SQL syntax errors if the script was executed on a server. (Bug #52743)

  • In the SQL Editor, if a routine was altered in the routine editor, it was possible to close the editor without the editor prompting you to save any changes made, and so changes were lost. (Bug #52728)

  • The Triggers tab in the Alter Table dialog of the SQL Editor erased all entered code, when an attempt was made to copy and paste text within the tab. (Bug #52587)

  • The Data Dump facility in the Administrator exported the entire schema into a single file when the Dump Views option was selected. Further, if tables were selected and the Dump stored routines option selected, the routines would be stored in their own file, but with the DROP PROCEDURE IF EXISTS statements missing. (Bug #52579)

  • During the import procedure of the Data Dump facility in the Administrator, stored routines were not imported. (Bug #52577)

  • The Connection Information panel in the SQL Editor did not display information for the User field. (Bug #52560)

  • MySQL Workbench crashed when an attempt was made to create an EER Diagram from a database containing a large number of tables (1500+). (Bug #52500)

  • MySQL Workbench crashed if No in the Delete Object dialog was clicked when attempting to delete a view from an EER Diagram. (Bug #52310)

  • In the SQL Editor, if in the Alter Routine dialog, the user had a routine that contained an error, the routine would be lost if an attempt was made to close the Alter Routine dialog using the close button, and then click Yes to apply changes. (Bug #51921)

  • In the Alter Table dialog of the SQL Editor, in the columns or indexes tab, the first right-click in the dialog central area failed to display the context-sensitive menu. However, it was displayed on subsequent clicks. (Bug #51796)

  • In the SQL Editor, it was not possible to export a result set, if the result set was not the first result set. For example, if there were two result sets, it would be possible to export the first one created, but not the second result set. (Bug #51595)

  • In the Object Explorer of the Sidebar, if an existing table was right-clicked, the context-sensitive menu displayed the option Create Table.... However, selecting this option appeared to have no effect. (Bug #51570)

  • In the SQL Editor, in the results editor, it was not possible to edit or copy data containing multiple lines of text. Further, lines containing new lines were displayed as if the new lines did not exist.

    MySQL Workbench now includes a blob editor. This can be accessed by right-clicking in the field to edit and selecting Open Value in Editor. (Bug #51561)

  • In the Alter Routine dialog of the SQL editor, there was inconsistency between the operation of the close dialog button ('X') on the top right of the window, and the Close button on the bottom right. When using the close dialog button you were prompted to save changes, regardless of whether you actually changed the routine or not. When using the Close button, the user was not prompted, even if the routine had changed. (Bug #51518)

  • The Message Log text area in the Forward Engineer to Database wizard was in active, preventing scrolling of the message when an error occurred. (Bug #51417)

  • In the SQL Editor, right-clicking a row in the results editor (after double-clicking a table), and selecting delete from the context-sensitive menu, did not have any effect. (Bug #51361)

  • The scrollable boxes on the Home screen did not respond to mouse wheel events. (Bug #51213)

  • When editing a row in the SQL Editor, if a column was NOT NULL and had a default value, and a value was not entered for it, then after changing another column if changes were applied an error would be generated. This was because the editor attempted to set the NOT NULL column to NULL, rather than to its default value. (Bug #50781)

  • The Log text area in the Reverse Engineer SQL Script wizard was inactive, preventing the log message from being scrolled. (Bug #50758)

  • The model Navigator did not redraw itself correctly. The Navigator worked correctly for the first model loaded into MySQL Workbench, but not for subsequently loaded models. (Bug #50580, Bug #50622)

  • When editing a table in the SQL Editor, the context sensitive menu items did not affect the row under the cursor, but a previously selected row. This potentially led to the unintentioned deletion of a row. (Bug #50113)

  • On the Linux platform, no context-sensitive menu was displayed when right-clicking a schema tab in the Physical Schemata section of the MySQL Model page. (Bug #49429)

  • In the EER Diagram view, when a table with a name containing underscores was right-clicked, the context-sensitive menu displayed menu items containing the table name without the underscores. (Bug #49314)

  • In the MySQL Model page it was not possible to delete a schema by using the context sensitive menu in the Physical Schemata section. (Bug #48055)