Documentation Home
MySQL Workbench Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 0.8Mb
PDF (A4) - 0.8Mb
EPUB - 237.2Kb

MySQL Workbench Release Notes  /  Changes in MySQL Workbench 5.2  /  Changes in MySQL Workbench 5.2.17 (2010-04-02)

Changes in MySQL Workbench 5.2.17 (2010-04-02)

This section documents all changes and bug fixes applied since the release of 5.2.16.

Functionality Added or Changed

  • The Execute Current Statement command in the SQL Editor has been improved. The statement that contains the cursor will be executed. Further, if the cursor is outside of a statement, the last statement before the cursor is executed. (Bug #52302)

  • If MySQL Workbench attempts to connect to MySQL Server version 4.x, an error message is generated to indicate this version is not supported. (Bug #51455, Bug #51844)

  • MySQL Workbench has been changed so that it is possible to run the start, stop, and check status scripts executed from the Administrator, with administrator privileges. A check box has been provided to enable you the option of acquiring the administrator rights to execute the commands. This option is switched off by default for the check status command. (Bug #51276)

  • A description column has been added to the snippets table. (Bug #51010)

  • The WeifenLuo library was removed. This was the cause of difficult to trace application crashes. (Bug #50706)

  • Various improvements to the SQL Editor user interface, including additional context-sensitive menu items in the Object Explorer, additional buttons in the Create Table and Alter Table dialogs, and more clearly displayed error messages. (Bug #50637, Bug #49918)

  • The MySQL Workbench installer now includes a Launch Now check box. By default, this is selected, so MySQL Workbench will be launched when the installer exits. (Bug #50387)

  • In the SQL Editor, the Comments tab in the Create View dialog has been removed. (Bug #49270)

  • The Output window only appeared in the Model context. MySQL Workbench has been changed so that the Output window now has its own tab on the main screen. (Bug #48988)

Bugs Fixed

  • In the SQL Editor, the wrong table was displayed when using EDIT. This happened if two schemata contained tables with the same name. For example, if two schemata, schema1 and schema2 both contained a table t1, then if the following SQL was entered and executed, schema2.t1 would be displayed instead of schema1.t1:

    use schema1;
    edit t1;

    (Bug #52401, Bug #52692)

  • If, in the EER Diagram view, an attempt was made to edit two tables, MySQL Workbench crashed. (Bug #52158)

  • In the EER Diagram view, when the menu item Model, Diagram Properties and Size was selected from the main menu, MySQL Workbench crashed. (Bug #52065, Bug #52375)

  • The Alter Table dialog in the SQL Editor displayed comments with a single quote character prepending it, and with the last character of the comment truncated. (Bug #51972, Bug #52297)

  • MySQL Workbench crashed when synchronizing a model to a live server. (Bug #51892)

  • MySQL Workbench crashed while attempting to edit code in the SQL Editor. (Bug #51815)

  • The New Server Instance wizard did not set the correct name for the startup script, when the installation type was set to Fedora Linux (Vendor Package). Testing the connection resulted in the error Operation failed: /etc/init.d/mysql start is invalid. (Bug #51802)

  • In the Object Explorer of the SQL Editor, right-clicking a table displayed the menu option Send to SQL Edtor. Editor was spelled incorrectly. (Bug #51790)

  • When synchronizing a model containing a large number of Stored Routines, not all routines were synchronized with the live server. (Bug #51731)

  • When synchronizing between two triggers, unexpected USE statements and the comment -- Trigger DDL Statements appeared intermittently. This caused a syntax error in the script. (Bug #51728)

  • If a connection was opened for querying and then Control+W quickly pressed to close the connection, MySQL Workbench would crash. (Bug #51685)

  • When opening the ip2nation.sql file MySQL Workbench crashed. (Bug #51606, Bug #51531)

  • Exporting a result set to a CSV file resulted in a file with a trailing comma appended to each line including the heading. (Bug #51594)

  • In the Inserts tab of the Table Editor, if a row was right-clicked and Delete selected rows selected, MySQL Workbench crashed. (Bug #51584)

  • MySQL Workbench crashed if objects were sequentially selected in the EER Diagram view. (Bug #51573)

  • In the SQL Editor, when an SQL query was entered that contained a large number of characters, it appeared full width in the action column of the Output tab, causing the Response column to be unacceptably narrow. (Bug #51550)

  • In the Alter Table dialog of the SQL Editor, if a column was added to a table, and then an attempt made to alter that column's data type, the wizard generated ADD COLUMN code, rather than CHANGE COLUMN. That resulted in this error when an attempt was made to apply the changes:

    ERROR 1060: Duplicate column name 'test_column'

    (Bug #51516, Bug #51719)

  • In the Alter Table dialog of the SQL Editor, when a table was edited and changes applied, if subsequent changes were made and applied an error would result, as MySQL Workbench attempted to use ADD COLUMN rather than CHANGE COLUMN. (Bug #51481)

  • When Manage Import / Export was clicked on the Home screen, a server instance selected, and then OK clicked, MySQL Workbench displayed an error dialog with this message:

    MySQL Workbench has encountered a problem, External component has thrown an

    (Bug #51477, Bug #51665, Bug #51703, Bug #51733, Bug #51800, Bug #51870, Bug #51895, Bug #51963, Bug #51944, Bug #51999, Bug #52052, Bug #52262)

  • Building MySQL Workbench from source failed if LDFLAGS="-Wl,--as-needed" option was specified. (Bug #51469)

  • If a long running SQL query was executed in the SQL Editor, and then the SQL Editor tab closed, MySQL Workbench crashed if a new connection was started from the Home screen. This exception was generated:

    Unknown Exception: caught in c:\documents and
    at line 1087

    (Bug #51467)

  • It was not possible to connect to the MySQL server with MySQL Workbench if using sockets. (Bug #51419, Bug #51460)

  • When a model with a view was exported using File, Export, Forward Engineer SQL CREATE Script, a semicolon was added to the end of the CREATE VIEW statement, even if one was already present from the view code entered. (Bug #51416)

  • On the MySQL Model tab, if a table was clicked on and edited using the context menu option Edit Table, MySQL Workbench crashed. (Bug #51410, Bug #50936)

  • If all screens and tabs were closed in MySQL Workbench and then Data, Manage Connections selected, then when the Manage DB Connections dialog was closed an unknown exception occurred. (Bug #51403)

  • If a server instance was created with the New Instance wizard with SSH disabled, this exception occurred when attempting to administer the server instance:

    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)
       at System.Windows.Forms.Control.OnMouseClick(MouseEventArgs e)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam,
    IntPtr lparam)

    (Bug #51368, Bug #51476, Bug #51522, Bug #51483, Bug #51978, Bug #51810, Bug #51883, Bug #51803, Bug #52115, Bug #52163, Bug #51292, Bug #51668, Bug #51784, Bug #51789, Bug #51940, Bug #51947, Bug #52021, Bug #52028, Bug #52108, Bug #52240)

  • After exporting a schema to disk, importing the schema did not restore the tables. (Bug #51261)

  • In the Routine Editor, the editor added // as the last delimiter, even though DELIMITER $$ was used at the beginning of the code. (Bug #51247)

  • In the SQL Editor, if a foreign key name was changed using the Foreign Key tab or Indexes tab of the Alter Table dialog, this error was generated:

    Type mismatch: expected type string, but got list

    (Bug #51192)

  • When the MySQL Workbench source was configured, the package gnome-keyring-1 was not found. (Bug #51090)

  • There were discrepancies between the list of pre-requisite packages given on the MySQL Workbench website and those listed in the README file in the MySQL Workbench distribution. (Bug #51085)

  • On the Output tab of the SQL Editor, it was not possible to properly view the contents of the Action and Message columns, if the text exceeded the standard column width.

    MySQL Workbench has now added a detail panel, so that long messages can be easily viewed. (Bug #51040)

  • In the Administrator section of MySQL Workbench, if a new user was created, the password was not correctly applied for the account, resulting in the new user being denied access when an attempt was made to connect to a server with that user account. (Bug #50983, Bug #51464)

  • An Out of Range exception occurred when switching from the Table Editor to the Home screen. (Bug #50980, Bug #51030)

  • In the Output tab of the SQL Editor, if a query produced an error response, it was difficult to read the returned error message. The message could only be read using mouse-over in the Response column, and the error message text could not be copied. The Response column is now renamed to Message. Further, the Message column has been widened, and new Action and Message detail panels have been added, making it easier to read error messages. (Bug #50629, Bug #50860)

  • When using the main menu item Scripting, Run Workbench Script File, the dialog appended .lua to the selected file name. This resulted in a failure to load the desired file. (Bug #50501)

  • In the SQL Editor, field names containing an underscore were displayed incorrectly on the Results tab. Instead of the underscore being displayed in the correct location the following character appeared underlined. (Bug #50132)

  • When a schema with Foreign keys and associated automatically generated foreign indexes was exported with the Skip Creation of FOREIGN KEYS check box selected, the generated script still contained the indexes. (Bug #49987)

  • In the SQL Editor, in a result set tab it was not possible to copy values from the result set. MySQL Workbench now includes the context sensitive menu items Copy row values and Copy field content. (Bug #49683, Bug #50170)

  • The Table Editor, Routine Editor, and other object editors stayed open, even if the user switched from the MySQL Model page to the SQL Editor page, Home screen, or Administrator page, thereby causing confusion. (Bug #49367)

  • In the live editing tab of the SQL Editor, if the Alt+Tab key combination was used, the ascending and descending sort order of the columns could no longer be changed. (Bug #49366)

  • The live data editor in SQL Editor did not permit the columns to be sorted in descending order by clicking the column heading. It only permitted column sorting in ascending order through clicking the column heading. (Bug #49302)

  • In the Overview tab of the SQL Editor there was no scrolling facility available. This meant that if the model contained a large number of schema objects the panel area was quickly filled, and it was not possible to view all of the objects without the ability to scroll. (Bug #49290, Bug #51634)

  • In the Alter Routine dialog of the SQL Editor, when a routine was changed, and the changes successfully applied using the Apply SQL Script to Database dialog, the Alter Routine dialog still prompted the user to apply changes, even though the changes had already been successfully applied. (Bug #49273)

  • When switching from a tab such as the SQL Editor tab to the Home screen, the toolbar did not change accordingly. However, the buttons on the toolbar were still active, leading to the possibility of unintentional actions. (Bug #49147)

  • In the SQL editor, if Alter Table was invoked for a table, and then the partitioning tab selected and partitioning enabled, it was possible to select a partition count of 0, which then generated an error if an attempt was made to apply changes. (Bug #49050)

  • This bug occurred when using the MySQL Workbench Administrator with MySQL Server version 5.0. When selecting Enable General Log in the Administrator's configuration page, MySQL Workbench attempted to add the option general-log to the configuration file, even thought this is not supported by MySQL Server 5.0. (Bug #49011)

  • In the Overview tab of the SQL Editor, if there were a large number of schemata, it was not possible to access certain schemata because they did not all fit on the schema tab control.

    MySQL Workbench has been changed so that there is now a small drop down control that enables you to select the required schema, even if it is not currently visible on the schema tab control. (Bug #48898, Bug #50169)

  • In the EER Diagram view, when zooming in or out of the diagram the screen was not redrawn correctly. (Bug #48020, Bug #48032, Bug #34505)

  • When using the option Omit Schemata Qualifier in Object Names in the Forward Engineer dialog, the schema name still appeared in DROP, CREATE SCHEMA, INSERT and USE statements. The schema name also appeared in the table comments. (Bug #46837, Bug #51411)

  • In the configuration settings panel of the Administrator, the ',' character was treated as part of the database name, and so it was not possible to specify multiple databases for certain configuration options.

    MySQL Workbench has been changed as follows:

    Several configuration options permit multiple databases to be specified. For example, binlog-do-db and binlog-ignore-db. However, if a comma is used to delimit these databases, the comma is correctly treated as part of the database name. This means that to specify multiple databases you must use multiple instances of the option.

    To specify multiple instances of the option, the “;” character can be used in MySQL Workbench. When text is entered into the option entry field and the “;” symbol detected, MySQL Workbench prompts you to select multiple instances, or leave the option entry unchanged. If selected the option will be written to the configuration file as multiple instances. Further, when a multiple instance option is detected in a configuration file it is parsed into <value1> ; <value2> ; ... ; <valueN>. (Bug #15245, Bug #11745436)

Download these Release Notes
PDF (US Ltr) - 0.8Mb
PDF (A4) - 0.8Mb
EPUB - 237.2Kb