MySQL Workbench Release Notes  /  Changes in MySQL Workbench 6.1  /  Changes in MySQL Workbench 6.1.1 (2014-01-23, Beta)

Changes in MySQL Workbench 6.1.1 (2014-01-23, Beta)

This is the first public release of the 6.1.x branch. It includes fixes from the 6.0.x branch up to 6.0.9.

Functionality Added or Changed

  • A MEB interface now allows MEB users to be added, configured and validated inside MySQL Workbench so that a user has the correct privileges to operate MEB. (Bug #17314254)

  • Dragging objects from the schema tree to the code editor now inserts the object name at the drop position. For example, dragging a table object will insert the table name. (Bug #11766411, Bug #59514)

  • Files can now be dragged and dropped into MySQL Workbench, which opens the file in a new SQL editor tab. (Bug #11760313, Bug #52710)

  • The restore operation can restore to a different schema. (Bug #11759068, Bug #51351)

  • A caption can now have a solid background in classic relationships and/or tables. (Bug #11753926, Bug #45452)

  • Comments added with the File, Export, Forward Engineer SQL CREATE Script... action would not be transferred to the generated SQL file. (Bug #11748708, Bug #37174)

Bugs Fixed

  • Sometimes, when exporting an EER diagram to SQL, the generated SQL code did not include "DROP SCHEMA" statements even with the Generate DROP SCHEMA option checked. (Bug #18054932, Bug #71243)

  • On Linux, the Cancel button was written as "Cance" on some systems, depending on the GTK theme used on the system. (Bug #18042862, Bug #71106)

  • Ubuntu 13.10 is now supported. (Bug #18042416, Bug #71281)

  • MySQL Workbench now builds on Debian 7.0-unstable. (Bug #18041235, Bug #71156)

  • One tab could execute the query from a different tab, after swapping tabs. (Bug #17903147, Bug #71029)

  • From MySQL Notifier, and with multiple MySQL instances installed, clicking Configure Instance... from MySQL Notifier, and then choosing the instance to configure in MySQL Workbench, could crash MySQL Workbench. (Bug #17853197)

  • On Linux, renaming foreign keys and indexes would crash MySQL Workbench. (Bug #17841664, Bug #70977)

  • Executing a DROP failed when multiple views were selected in the schema navigator panel. For example, selecting two views would generate an error such as "join() takes exactly one argument (2 given)". (Bug #17840809, Bug #70978)

  • Toggling the Additions and Output panel as hidden is now preserved across MySQL Workbench sessions. (Bug #17833296, Bug #70965)

  • On Linux, building MySQL Workbench from source would generate many glib related warnings with newer versions of glib. (Bug #17813170, Bug #70932)

  • After creating a new view inside a model, clicking Add View would display a new view in the editor this new could not be saved. (Bug #17796027, Bug #70904)

  • The --routines command line option was missing from the generated mysqldump command when multiple schemas were selected for a dump into a single file backup when the routines option was enabled. This could happen after executing the dump multiple times. (Bug #17795551, Bug #70896)

  • Executing Model, Forward Engineering with the Do not create users, only export privileges option enabled would recreate the user instead of simply changing privileges for the existing user. (Bug #17794653, Bug #70903)

  • When building from source and without building the documentation, the documentation link will open the online MySQL Workbench manual. (Bug #17788936, Bug #70873)

  • Adding a new table to an empty EER diagram would crash MySQL Workbench. (Bug #17775383, Bug #70872)

  • On OS X, switching colors with layers and tables several times could eventually cause a crash. (Bug #17758312, Bug #70841)

  • Opening MySQL Workbench from the MySQL Notifier by choosing SQL Editor on a remote MySQL connection could crash MySQL Workbench. (Bug #17751731)

  • MySQL Workbench displayed an empty binary string as NULL. (Bug #17741282, Bug #70817)

  • The Inserts tab under Forward Engineering would sometimes unexpectedly fail. (Bug #17698069, Bug #70747)

  • The ENUM type now corresponds better to its definition better under Model, User Defined Types, to allow arguments. (Bug #17633506, Bug #70671)

  • On Microsoft Windows and OS X, the bundled PyCrypto library was upgraded to version 2.6.1. (Bug #17615430)

  • If a Linux box had multiple MySQL instances running, the status would be reported as "running" for all instances even if only one or more of them were running. (Bug #17516593)

  • MySQL Workbench could crash when using a MySQL connection that connects via an SSH tunnel with success, but is defined using incorrect MySQL server credentials. A dialog now requests the correct information. (Bug #17456433, Bug #70332)

  • Having a long comment (more than 60 characters for table, or more than 255 characters for a column) in the model, single quotes or newlines after this length would result cause Forward engineer SQL Alter Script... to not include objects after the offending comments in the exported file. (Bug #17455899, Bug #69776)

  • Attempting to change a trigger name in an EER Diagram would crash MySQL Workbench. (Bug #17425655, Bug #70257)

  • The catalog treeview for an EER diagram was replaced by a central control with improved handling, which allows MySQL Workbench to worth more smoothly with a large number of tables. (Bug #17370413, Bug #69692)

  • Opening a valid MySQL connection would sometimes yield a window with a wide SQL editor panel. (Bug #17300438)

  • Under certain scenarios, the File, Print to File... action would not allow models to be unchecked. (Bug #17300434)

  • On OS X, opening a local MySQL connection to a MySQL server that was unavailable would generate an unhandled exception. (Bug #17300002)

  • Indexes that were auto-created for a Foreign Key can now be deleted in case another suitable index was available. (Bug #17275827, Bug #69937)

  • On OS X, an option to Disable column Resizing or continue is now displayed when a query is determined to display too many columns. This works around a Cocoa issue that could potentially freeze MySQL Workbench. (Bug #17085770, Bug #69613)

  • Model synchronization would complete, but if repeated then MySQL Workbench would ask to update the database again. (Bug #17033354, Bug #69591)

  • Changing the collation type would not always be detected, as "No changes detected" would be reported after attempting to apply the change. (Bug #16492371, Bug #68672)

  • On OS X, right-clicking inside the code area of the Script editor did not provide the copy and paste commands. (Bug #16276986)

  • The MySQL Forums link on the MySQL Workbench home page was updated, and it now links to a MySQL Workbench page that also links to the MySQL Workbench - Database Migration forum, when before it was difficult to find. (Bug #14773380, Bug #67272)

  • From Database, Reverse Engineer, and after selecting a schema with multiple tables, clicking the left or right arrow buttons with the Show Filter feature to include/exclude tables would lose the cursor position, and always move the cursor to the top of the list. (Bug #14017237, Bug #65018)

  • For models, tables can now be renamed by double-clicking the name column, and the columns edited. (Bug #13702831, Bug #64134)

  • MySQL Workbench could crash after choosing Recover when prompted to recover a model file from a previous session after MySQL Workbench was not closed properly. (Bug #13051204, Bug #62589)

  • A large SQL script file could not be saved for a model, although a limit of around 200MB limit still exists. (Bug #13025333)

  • Applying an large SQL Script object to a model could crash MySQL Workbench. (Bug #13025299)

  • The full path to the model file is now displayed in the Models section in the home page. (Bug #12616312, Bug #61349)

  • On Linux, executing Export to Disk with a custom ~/my.cnf present would cause the export to fail. (Bug #12613307, Bug #58526)

  • The temporary table created would only include one column ID rather than the full table when a view statement contained a subquery. This caused processing problems when attempting to use the exported scripts.

    A workaround was to recreate the view object by deleting the dependent view definitions and replacing them with new view definitions. (Bug #11765994, Bug #59018)

  • The "Scratch" SQL editor tabs were removed, and instead standard SQL editor tabs are always opened. (Bug #11765876, Bug #58882)

  • Importing an invalid model could crash MySQL Workbench, but now an error is generated. (Bug #11765756, Bug #58752)

  • On Microsoft Windows, opening and closing models/diagrams would increase the number of open GDI (Graphics Device Interface) objects as they were kept in memory for the undo queue. The required memory for this task was decreased. (Bug #11765437, Bug #15998212, Bug #58405, Bug #67870)

  • Editing a mandatory relationship now updates the referenced column. (Bug #11764011, Bug #56792)

  • On the index tab in the table editor, the option to change the "PRIMARY" text had no effect. (Bug #11761805, Bug #54331)

  • General sorting improvements were made to the SQL statement results matrix, including changes to remove variances with different platforms. A selected column stays set after a sort, and selecting a column while holding Shift adds the column to the sort criteria, thus sorting by multiple columns. (Bug #11760178, Bug #52561)

  • The Schema Privileges tab was hidden in the Schema editor, and is now more viewable. (Bug #11758814, Bug #51066)

  • The Copy and Paste keyboard shortcut did not always function from within table cells in all environments. (Bug #11755245, Bug #46994)

  • Zooming out from an EER diagram would also reduce the size of the associated tooltips, which rendered the tooltips unreadable. (Bug #11749683, Bug #39609)