• Sixth GA release of 5.2. This section documents all changes and bug fixes that have been applied since the release of 5.2.30.

    Functionality added or changed:

    • MySQL Workbench has been changed so that holding the spacebar while in the EER Diagram view temporarily changes the cursor to the hand tool. When the spacebar is released the cursor reverts to the tool that was selected prior to the spacebar having been pressed. (Bug#52331)

    Bugs fixed:

    • Typing into the Workbench Scripting Shell resulted in an Unexpected Error:
      MySQL Workbench has encountered a problem.
      Attempted to read or write protected memory. This is often an indication that other
      memory is corrupt.


    • In the Administrator, monitoring of a remote server did not work. (Bug#58586)
    • In the Query Editor, using the beautifier on a query resulted in an unhandled exception. (Bug#58565)
    • In the Administrator, when the monitored server was started or stopped, the following error message was generated:
      Could not stop/start server: expected a character buffer object


    • In the SQL Editor, when the beautifier was run on code containing several statements, the code was incorrectly formatted. (Bug#58367)
    • In the SQL Editor, a query containing a CASE keyword was not handled correctly by the query formatter. (Bug#58361)
    • In the SQL Editor, the query formatter converted certain tokens to uppercase that should not have been converted. (Bug#58360)
    • In the Query Editor, if a query was partially selected, and then the beautifier run, the results were unpredictable. Problems included exceptions, duplicated tokens, and incorrect indentation. (Bug#58359)
    • In the SQL Editor, if a query was written in the SQL Query tab, and then highlighted using the cursor, the query formatter failed with an unhandled exception on calls to beautify, uppercase or lowercase functions. (Bug#58358)
    • When attempting to beautify a CREATE INDEX query, the query beautifier removed part of the query. (Bug#58357)
    • In the SQL Editor, when using the Beautify query facility on a CREATE TABLE statement, an unhandled exception was generated. (Bug#58356)
    • In the SQL Editor, using the code beautifier on a query containing USING resulted in an invalid query being generated. This was due to missing spaces around USING. (Bug#58347)
    • Autotools were required to be installed locally in order to build MySQL Workbench from source. (Bug#58263)
    • The MySQL Workbench tarball contained cached Autotools information. (Bug#58261)
    • In the SQL Editor, right-clicking on a table name and selecting Alter table did not launch the Alter table dialog as expected. This happened if the table name utilized mixed case letters. (Bug#58223)
    • In the Reverse Engineer SQL Script wizard, on the Input and Options page, the button to select the SQL script file had the text “Brow” instead of “Browse”. (Bug#57929)
    • The commands to arrange objects were not enabled in the EER Diagram view. This rendered it impossible to move objects to the back or bring them to the front. (Bug#57907)
    • When setting the data type of a column to DOUBLE with precision specified, the data type reverted to DOUBLE without the desired precision specifiers. This happened in both the Table Editor and the SQL Editor. (Bug#57865)
    • In the columns tab of the Table Editor, double-clicking to edit or add a new column caused the window to scroll to the top. (Bug#57793)
    • In the SQL Editor tab of the Workbench Preferences dialog, it was possible to accidentally select or deselect one of the options Treat BINARY/VARBINARY as nonbinary character string orEnable Data Changes Commit Wizard, if the OK button was not clicked centrally. (Bug#57669)
    • The forward engineering process generated SQL code that quoted boolean values, causing incorrect cast values. When a table contained the logical BOOLEAN type for a field it was converted to TINYINT(1) as expected. However, the values that were supplied for any inserts were quoted, as in the following example:
      INSERT INTO mytable (id,flag) VALUES (NULL,'TRUE');


    • In the SQL Editor, if a query ran longer than 30 seconds the following errors were generated:
      Error Code: 2013  Lost connection to MySQL server during query
      Error Code: 2006  MySQL server has gone away


    • On the Select Object page of the Reverse Engineer Database dialog, the panels displayed whenShow Filter was clicked, did not resize correctly when Hide Filter was clicked. (Bug#57376)
    • The MySQL Configuration file could not be accessed during MySQL Workbench installation. (Bug#56987)
    • When the MySQL service was set to manual in MySQL Workbench, the service was displayed as running in the server status panel, even though the service had not yet been started. (Bug#56919)
    • When creating a new server instance, the following error occurred on testing settings:
      Operation failed: File  doesn't exist


    • Find and Find and replace did not work in the SQL Query tab. (Bug#56898)
    • Creating a many-to-many relationship between two tables resulted in only one index being generated. (Bug#56613)
    • MySQL Workbench crashed when a snippet in the snippet list was right-clicked. (Bug#56588)
    • When saving over a read-only file, MySQL Workbench changed the file permissions to read-write. (Bug#56403)
    • If the Table Editor was resized, it returned to the default size when switching between tables to be edited. (Bug#56314)
    • MySQL Workbench attempted to reconnect to a connection that had previously been closed in the SQL Editor, after the computer woke from the sleep state. (Bug#56302)
    • In the Connections tab of the Administrator, scrolling did not work correctly when there were large numbers of connections. (Bug#56144)
    • When multiple tabs were open in the Administrator, each connected to a different server, and export of a database was set up in each tab, running an export operation resulted in errors. This was due to the fact that MySQL Workbench attempted to export a database selected in a tab other than the currently selected one. (Bug#56113)
    • If a MWB file was double-clicked to open, but MySQL Workbench was already running, a new instance of MySQL Workbench was launched, rather than opening the file in a new tab in the currently running instance. (Bug#56067)
    • In the SQL Editor, in the Foreign Key tab of the new-table dialog, it was not possible to select any of the foreign key checkboxes. (Bug#56024)
    • Close tab functionality failed intermittently. This occurred when attempting to close the tab directly, or when using the File, Close tab menu item. (Bug#55901)
    • In the sidebar of the SQL Editor, when a default schema was selected, other schemas listed in the sidebar were not displayed. (Bug#55864)
    • In the Administrator, most columns were not sortable. For example, in the Connections tab, it was not possible to sort connections based on clicking the columns id, User, Host, DB, Command, Time, State, Info. (Bug#55813)
    • When an EER diagram that was in the background was closed, it was not possible to reopen it. (Bug#55767)
    • If the relationship editor was already open, it was not possible to open the relationship editor for another relationship, without closing it first. (Bug#55708)
    • The environment variable PYTHONPATH from other Python installations interfered with MySQL Workbench. When starting MySQL Workbench the error “cannot open SSH Tunnel Manager” appeared. Further, it was not possible to use the administrative functions of MySQL Workbench. (Bug#55674)
    • In the EER Diagram view, a copied object could not be pasted, if the object had previously been pasted and then edited. (Bug#55336)
    • Selecting a Refresh or Refresh all button or menu item caused the list of tables and views in the sidebar to become empty. (Bug#55214)
    • In the Configuration tab of the Administrator it was not possible to enable or disable the local_infile (LOAD DATA LOCAL) option. (Bug#55031)
    • In the Administrator, system health displayed NO DATA. (Bug#52151)
    • When using the Administrator, the CPU utilization jumped to 50%. (Bug#50578)
    • After printing, the status message displayed included incorrect capitalization. “Print Diagram done” should have been displayed as “Print diagram done”. (Bug#50035)
    • The schema editor decreased in size by several pixels each time a new schema was edited. (Bug#49425)
    • The SQL Editor did not display the execution times for queries. (Bug#49390)
    • The menu option View, Windows, menu item did not appear to have any useful function. (Bug#49056)

      View the Complete List of Changes »

      Download Now »

Post By Gishore J Kallarackal (2,121 Posts)

Gishore J Kallarackal is the founder of techgurulive. The purpose of this site is to share information about free resources that techies can use for reference. You can follow me on the social web, subscribe to the RSS Feed or sign up for the email newsletter for your daily dose of tech tips & tutorials. You can content me via @twitter or e-mail.

Website: → Techgurulive