Changes in MySQL Workbench 5.2.12 (Not released)

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

• Functionality Added or Changed

• Bugs Fixed

Functionality Added or Changed

• In the SQL Editor, if a table was edited with the Edit Data facility, and table values changed, no warning was given if an attempt was made to close the tab without having first applied changes using the apply button.

  MySQL Workbench has been changed so that if the user attempts to close a live editing tab, without having applied any changes made, a warning dialog is displayed. (Bug #49925)

• MySQL Workbench has been changed to permit a connection to be created where the password does not have to be stored. In this case, MySQL Workbench prompts the user to enter the correct password when the connection is established. (Bug #49409)

• Undo operations are no longer tracked in the editors that work with live databases, such as table editors within the SQL Editor. (Bug #49284)

Bugs Fixed

• Security Fix: The password for the connected MySQL Server was exposed by the SQL Administrator in MySQL Workbench. The password was displayed in plain text form in the Startup Message Log on the Startup tab of the Admin page. (Bug #43287)

• In SQL Editor, SELECT statements that called functions, for example SELECT md5('abcd'), did not give the expected result. (Bug #50248)

• In the Table Editor, the list for selecting the table engine type contained a reference to calpont. This should now be infinidb. (Bug #50159)

• In OS X, the context-sensitive menu was missing from the live editing tab of the SQL Editor. Right-clicking in the editing tab simply displayed a OS X menu, rather than the context-sensitive menu to enable actions such as copying, deletion and setting selections to NULL. (Bug #50114)

• On the Model page, if some text was entered into a note in Model Notes, and then the model was saved and closed, on reloading the note would be empty.

  This also happened for a script added in SQL Scripts. After the model was saved and reloaded, the script would be empty. (Bug #50108)

• Custom Python modules failed to load and were not displayed in the MySQL Workbench Plugins menu.

  In MySQL Workbench 5.2 the syntax used has changed from @wbplugin to @ModuleInfo.Plugin. (Bug #50108)

• The script code generated from a model for routines did not quote schema names in USE statements. (Bug #50051)

• Lower panels such as the Table Editor remained open, even when the user returned to the Home screen. (Bug #49926)

• In the SQL Editor, when using the Query, Export Results... menu item, the file extension was omitted when selection of an existing output file was made. (Bug #49870)

• After selecting Edit Table Data from the Home screen, and launching the Edit Table Data wizard, MySQL Workbench crashed if a connection was selected and then the Next button clicked. (Bug #49864)

• In the Manage DB Connections dialog, when attempting to create a Standard TCP/IP over SSH connection, errors occurred when testing the connection in the case where a key file had been specified. If the path to the key file was quoted the error was:

  Cannot open SSH Tunnel:  ERROR Invalid request

  If the same path was not quoted the error generated was:

  Could not connect SSH tunnel:  ERROR [Errno 22] invalid mode ('r') or filename:
  'D:\\Documents and Settings\\tf221715\\.ssh\\id_dsa'

  It should be noted that currently only key files using the OpenSSH format are supported. (Bug #49812)

• In the SQL Editor, if a Stored Procedure was executed and then immediately executed again, this error was generated:

  Error code 2014
    Commands out of sync; you can't run this command now

  This problem only affected MySQL Workbench running on the OS X platform. (Bug #49553)

• Right-clicking a Routine Group and then selecting Copy SQL to Clipboard did not work. No code was copied to the clipboard. (Bug #49440)

• Opening a model file, closing it and quickly reopening it caused MySQL Workbench to hang. (Bug #49428)

• Clicking the Test Connection button in the Manage DB Connections dialog caused MySQL Workbench to lock up. The error generated on the console was:

  18743 INFO Connecting to SSH server at 127.0.0.1:22...
  Unhandled exception in thread started by <bound method Tunnel._threadloop of
  <__main__.Tunnel instance at 0x9acea8>>

  This happened for the connection method Standard TCP/IP over SSH. (Bug #49419)

• Two SSH tunnels were opened for a single connection to an SSH server. The user was also prompted for a password when a new connection was established, even when the existing tunnel was reused. (Bug #49412)

• SSH Tunnels opened by MySQL Workbench were never closed. SSH Tunnels created when clicking Test Connection in the Manage DB Connections dialog, were not closed. This was also the case when the SQL Editor and Server Administration tabs were closed. (Bug #49411)

• In the Partitioning tab of the alter table dialog it was possible to enter a number greater than 10 into the Partition Count textfield. However, when these changes were applied the DDL generated substituted any value entered that was greater than 10 with the value 2. (Bug #49380)

• MySQL Workbench generated an unhandled exception when trying to add a new column using the Alter Table facility in the SQL Editor. After the VARCHAR(45) column was added, without selecting any column check boxes, the exception occurred when the Apply button was clicked. (Bug #49364)

• If a database was reversed engineered from a source, and a table renamed, then although this change was detected by MySQL Workbench, no DDL code was generated if an attempt was then made to synchronize this change with the source. (Bug #49313)

• In the SQL Editor, when a schema was dropped, it was still displayed in the Overview tab and in the schemata explorer of the side panel. Further, MySQL Workbench did not provide any confirmation that the schema had been dropped successfully or otherwise. (Bug #49282)

• The Alter Schema dialog in the SQL Editor permitted the schema name to be changed using the Name textfield, even though doing this is not supported at the server level. (Bug #49281)

• In the SQL Editor, if an item in the History tab was right-clicked, and the menu option Append selected items to SQL script selected, MySQL Workbench generated an unhandled exception:

  glibmm-ERROR **:
  unhandled exception (type std::exception) in signal handler:
  what: vector::_M_range_check

  (Bug #49245)

• In the Create a new server instance wizard, if the check box Enable SSH login based administration was cleared, the wizard still prompted the user to enter an SSH password when the Next button was clicked. (Bug #49226)

• In the Server Status section of the Admin page, the SYSTEM graphic showed CPU usage at 50%, while the corresponding text label showed CPU usage at 0%. The graphic and label remained out of synchronization for around 15 seconds. (Bug #49212)

• In the SQL Editor if an EDIT table operation was being carried out, it appeared that data in the table was not updated, and also a row already inserted would be erroneously deleted when attempting to add a new row of data, when changes were applied.

  MySQL Workbench has been changed so that if an error occurs during changes being applied, an error dialog is displayed showing any errors that occurred. Also, the status text is now updated to say “Apply Failed”, rather than “Changes Applied”. (Bug #49179)

• The Manage DB Connections dialog did not prevent duplicate connection names or an empty string as a valid connection name. (Bug #49150)

• The toolbar buttons on the Home screen did not reflect the order of the action items in the Workspace. The Open Server Profile button and Open DB Connection Manager buttons needed to exchange positions. (Bug #49149)

• In the Logs tab of the Administrator, the Oldest and Newest buttons appeared to have reversed functionality. Oldest displayed the most recent timestamps and Newest displayed the oldest. (Bug #49065)

• In the Manage DB Connections dialog, many textfield labels appeared truncated. (Bug #49052, Bug #49378)

• The ID for a connection was displayed in the Connections tab of the Admin page, even after the corresponding administration session had been closed. (Bug #48989)

• The Connections list in the Manage Server Instances dialog did not display the user name for socket and pipe connections. For example it displayed Localhost - @:0 <Local Socket/Pipe>, rather than Localhost - root@:0 <Local Socket/Pipe>. (Bug #48969)

• Various errors occurred when attempting to modify the server configuration using the Configuration tab of the Administrator:

  Unhandled exception: global name 'tempfile' is not defined

  Unhandled exception: [Errno 22] Invalid argument:
  'C:\\users\\tax\\appdata\\local\\temp\\tmpo47ttn'

  Also, if the Logs tab was selected to view the server log files, this error occurred:

  Unhandled exception: Error executing 'Select @ @
  log_output': Unknown system variable 'log_output'

  (Bug #48906)

• In the Forward Engineer an ALTER Script wizard, the textfields and associated buttons for selecting input and output files were not positioned correctly within the window, when the selected file name was long. Although the files could be selected when the wizard was first launched, if the wizard was launched subsequently, the text fields would be filled with the previously selected file names, causing the textfields and Browse buttons to be located beyond the borders of the window.

  A similar problem also affected the Forward Engineer SQL Script wizard. (Bug #48222)

• In the Partitioning tab of the Alter Schema dialog, it was not possible to create a single partition. If a partition count of 1 was specified this was actually set to 2 in the generated DDL. (Bug #48114)

• When performing a Synchronize Model operation, all foreign key relationships in the EER diagram that had the setting draw split were redrawn as fully visible. (Bug #47767)

• When running MySQL Workbench from the command line, it could not open model files where the path contained a space. (Bug #46297)