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.41 (2012-07-25)

Changes in MySQL Workbench 5.2.41 (2012-07-25)

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

This version contains the initial release of the Database Migration Wizard.

Functionality Added or Changed

  • Added a new Data Import/Restore option to select the default schema to import to, and a button to create a new schema in case a dump is being imported from a single file. (Bug #13539030, Bug #63853)

  • A word wrapping option was added to the SQL Editor. (Bug #11765583, Bug #58566)

  • The Diagram object tooltip now displays the column comments. (Bug #11765060, Bug #57977)

  • A Global Privileges tab was added to the Server Administration interface. It allows adding and editing individual global user privileges. (Bug #11761628, Bug #54141)

  • Basic code completion functionality has been implemented. (Bug #11760500, Bug #13813099, Bug #52917, Bug #64525)

  • The model wizards now remember the last connection that was added. (Bug #56515, Bug #11763761)

  • MySQL Workbench added a migration wizard, which will migrate ODBC compliant databases to MySQL. (Bug #54731, Bug #11762168)

Bugs Fixed

  • The Search on Server option would not function, and instead it generated errors when searching MySQL Server 5.1. This option is now only available when connecting to MySQL Server 5.5 or greater. (Bug #14404138)

  • MySQL Workbench was not compatable with alocal versions greater than 1.11.1. Compiling would generate errors related to AC_RUN_IFELSE usage, as opposed to the preferred AC_LANG_SOURCE. (Bug #14329354, Bug #65898)

  • On Microsoft Windows 64-bit, closing MySQL Workbench from within the SQL editor could cause a crash. (Bug #14307316)

  • A snippets file could not be created. (Bug #14278287, Bug #65734)

  • The option to control specific user privileges is now available with MySQL Workbench. Before it was only possible to edit the roles (e.g., DBManager) but now the specific privileges (e.g., RELOAD) can also be modified. (Bug #14226955, Bug #65677)

  • Comments and collation controls are now disabled until a column in the column editor is selected. Before it was always available, so invalid entries would attempt to be created, which would result in an error. (Bug #14177412, Bug #65574)

  • It is now possible to select a range of rows using the shift key. And on Mac OS X, the command key will now allow the selection of individual rows (Bug #14177386, Bug #65569)

  • An orphaned privileges tab would be shown in the table editor when switching tables. Now only the current privilege tab is displayed. (Bug #14102537, Bug #65182)

  • The Edit, Find, Find and Replace operation was slow. (Bug #14079480, Bug #65262)

  • MySQL Workbench would not load with Ubuntu 11.10. (Bug #14058886, Bug #63626)

  • Having a schema without a name in a model would cause MySQL Workbench to crash. (Bug #14017357, Bug #65119)

  • Using the '%' character within environment variables could cause MySQL Workbench to crash. (Bug #13989371, Bug #65056)

  • MySQL Workbench failed to compile with automake 1.11.2 or greater, due to the pkglib_DATA reference. (Bug #13972001, Bug #63898)

  • Several exposed DbMySQL methods (such as makeSQLExportScript) were problematic, and have been replaced by the DbMySQLRE and DbMySQLFE modules. (Bug #13971951, Bug #62596)

  • The SQL Beautifier feature would remove DISTINCT from inner queries. (Bug #13970596, Bug #64932)

  • MySQL Workbench would crash while multiple model routines were opened. (Bug #13970497)

  • Creating and then synchronizing a table in a model with a DOUBLE typed column would generate invalid SQL, thus generating an "Invalid SQL syntax" error. (Bug #13970484, Bug #64990)

  • The SQL Beautifier would delete WITH ROLLUP if it was contained within a subquery. (Bug #13919924, Bug #64796)

  • The Replace All option would not function when the replacement string was empty. (Bug #13919875, Bug #64818)

  • On Linux and Mac OS X, it was not possible to select/copy multiple rows from within the result set grid. (Bug #13895191)

  • Passing a grt.classes.db_query_EditableResultset object to getattr() could cause a crash. (Bug #13893388, Bug #64777)

  • A new Copy Row (tab separated) option was added to the result set context menu within the SQL editor. A comma separated variant of this option already existed. (Bug #13884753, Bug #64724)

  • Certain conditions would cause privilege related problems and emit errors such as "Incorrect Value Entered" when creating a table in one tab, altering it in another, then going back to the original tab. (Bug #13877873, Bug #64591)

  • Using Paste Row after Copy Row Data within the SQL editor would insert rows with extra apostrophes. For example, 'hello' would become ''hello''. (Bug #13840070, Bug #64630)

  • Internal log tables are now excluded while exporting a the MySQL database. The excluded tables are mysql.schema, mysql.apply_status, mysql.general_log, and mysql.slow_log. (Bug #13837725)

  • Inputting invalid SQL would remain designated as such, even after the SQL was corrected. (Bug #13820997, Bug #64481)

  • Closing an SQL Editor tab that had a Find/Replace dialog box open, then subsequently closing the Find/Replace dialog box would crash MySQL Workbench. (Bug #13816167, Bug #64569)

  • Input elements are now correctly disabled until an editable row in the column editor is selected. Therefore, invalid values are no longer set in the model. (Bug #13812811, Bug #64550)

  • Changing the Default Collation of a schema after changing its name would reset the schema name to "new_schema". (Bug #13799456, Bug #64259)

  • The Edit table data SQL editor option would not properly display or save Unicode characters. (Bug #13790645, Bug #64447)

  • The Match Case search option did not function. (Bug #13790397)

  • All editor tabs now prompt to save data when these tabs are closed. Before, only the main tabs (like the SQL Editor) would prompt for to save. (Bug #13788071, Bug #64462)

  • Opening the Scripting Shell window, followed by selecting then closing the snippet tab, would cause MySQL Workbench to crash. (Bug #13744364)

  • If Plugins, Utilities, Indent Selected Lines is used while a row is selected, then MySQL Workbench would delete the selected row. (Bug #13744346)

  • On Mac OS X, the color dropdown in the object tool would not display the color properly. It instead showed the color code, and would not apply the color to the object. (Bug #13742905)

  • On Mac OS X, the Option key did not behave like a standard Mac OX application. For example, Option + Delete would delete one character instead of one word. (Bug #13702376, Bug #64217)

  • Added version dependent keyword list support for syntax highlighting. Supports MySQL Server 5.0, 5.1, 5.5, and 5.6 (Bug #13699804)

  • Quickly executing the same query multiple times would cause MySQL Workbench to use an excessive amount of memory and CPU. (Bug #13642999, Bug #64077)

  • On Mac OS X, and while working with mixed-case table names, a foreign key could not be assigned to link two InnoDB tables together. (Bug #13639162, Bug #64109)

  • The Model, Model Options, Diagram, Hide Captions option could not be altered (disabled) and would remain checked (enabled). (Bug #13571857, Bug #63937)

  • MySQL Workbench would allow the creation of multiple foreign keys across multiple tables but with the same foreign key name. Synchronization would then emit a "Can't create table" error. (Bug #13548236, Bug #13500447, Bug #63642, Bug #62960)

  • The Object Browser now manages procedures and functions separately, when before they could not co-exist with the same name. They remain under the routines group but have separate icons and menu options. (Bug #13548213, Bug #13730415, Bug #63849)

  • After right-clicking on a value in the SQL editor and choosing Open Value in Viewer, selecting the text would insert extra new lines into the clipboard. (Bug #13538942, Bug #63753)

  • The Server Administration, Server logs, General Log Table option would not function, and only show a Try again button. (Bug #13530413)

  • While editing in the Edit Table tab, Control + A would also select diagram objects. (Bug #13519852, Bug #63758)

  • A "Removed corrupt column definition for Foreign key" error would sometimes be emitted while editing a table with foreign keys. (Bug #13519797, Bug #63772)

  • OpenGL determination at startup has been disabled, and instead this check is performed while creating diagrams. The system could fail at startup, so now MySQL Workbench avoids this startup trouble and can better fall back to software rendering if necessary.

    MySQL Workbench would also silently fail to load if "Microsoft Visual C++ 2010 Redistributable Package" was not available. This is now checked and reported to the user. (Bug #13512714, Bug #61969)

  • The Open Value in Editor SQL editor option did not work with INT or NULL values. (Bug #13492493, Bug #62934)

  • Plugins, Utilities, Execute query would freeze MySQL Workbench if the query resulted in 1000 or more rows. (Bug #13470781)

  • The Move to a group context option for database connections would cause saved connections below the target connection (that is being added to a group) to disappear. (Bug #13470318)

  • The info and session tabs within the MySQL connection interface would not display any information. (Bug #13466537)

  • After making changes to a model, then closing the window, clicking Cancel on the unsaved changes warning/dialogue would close MySQL Workbench. Now the model window remains open. (Bug #13463465, Bug #63460)

  • The Options tab within the SQL Editor would always display an empty AUTO_INCREMENT value for tables using InnoDB. (Bug #13463458, Bug #63464)

  • On Mac OS X, Command + A would not select all results from the result set. (Bug #13463374, Bug #63461)

  • After synchronizing a database, refreshing a model would not refresh the stored procedure information. (Bug #13418563, Bug #62879)

  • The MySQL Workbench bug reporting form (MySQL Bugs: Report) did not allow pasting content into the form. (Bug #13344751, Bug #62928)

  • A query such as "SELECT * FROM SomeTable PROCEDURE analyse()" would only work if "limit rows" was disabled in the preferences. The MySQL Workbench query parsing has been extended to support this type of query. (Bug #13344686, Bug #62964)

  • "MariaDB" has been change to "Aria" within MySQL Workbench. (Bug #13252479, Bug #62903)

  • Routine groups on the diagram was not updated after adding new routines to the group. (Bug #13029520, Bug #62496)

  • On Microsoft Windows, Server Administration, Server logs, Slow Log File would display an error instead of showing the slow query log. (Bug #13026572)

  • The Connection Method option within the Edit Table Data window was partially hidden. (Bug #13025670)

  • Right-clicking on Catalog tree within the Model, Diagram context would display an empty line. (Bug #13025389)

  • Clicking between routines with different comments would not update the description editor with information from the selected object. (Bug #13025359)

  • MySQL Workbench would crash after clicking EER links and options multiple times. (Bug #13024949)

  • Detection of a connection to the local machine based on the IP address has been removed. There is now a selection between localhost, remote host, and db host on the initial New Server Instance page. Selecting localhost will let the wizard know that it is local, as otherwise the full path is now required, which for example allows to be used as a remote host to support port forwarding. (Bug #12890503, Bug #62119)

  • The sorting options within the Inserts Editor window did not function. (Bug #12884134)

  • The View, Home option did not function. (Bug #12879850)

  • User Defined Types (UDT) could not be deleted when they were not referenced elsewhere. (Bug #12671629, Bug #61530)

  • The MySQL Workbench window can now be resized to 1024x710. (Bug #12632406, Bug #60762)

  • A confirmation dialog was added that warns users about attempts to edit stub tables, and it describes why these will be ignored by both synchronization and forward engineering. The dialog includes an option to either keep editing it as stub object, or to clear the stub flag and make the table appear in generated SQL. (Bug #12616360, Bug #61309)

  • The synchronization wizard now allows the possibility to force synchronization of schemas that are thought to have been renamed. Otherwise, MySQL Workbench will recreate the schema from scratch. (Bug #12565644, Bug #61211)

  • The EER Diagram zoom feature would not function. (Bug #12346981, Bug #60807)

  • The Partitions tab within the Alter table context menu would not show all of the available partitions. (Bug #11933015, Bug #60235)

  • On Mac OS X, having a large number of databases (1,000+) could cause performance issues where MySQL Workbench would load in several minutes, as opposed to a few seconds. (Bug #11869432, Bug #60420)

  • MySQL Workbench would not allow a user to delete a saved server instance that contained an incorrect password. This incorrect password can now be deleted. (Bug #11765337, Bug #58295)

  • MySQL Workbench would freeze while attempting to search and replace with a large number of strings, such as over 100,000. (Bug #11762890, Bug #55539)

  • The Synchronize Model operation would use an excessive amount of memory. (Bug #11762726, Bug #55355)

  • A new Model: MySQL preference was added for Forward Engineering and Synchronization to configure SQL_MODE. (Bug #11761659, Bug #54173)

  • The Synchronization wizard has been changed to allow forcing synchronization of schemas that have the same name but an unexpected "last known name", which would cause a confusing scenario of the target database being recreated from scratch. (Bug #11756969, Bug #48962)

  • New or updated trigger content would disappear from the SQL Editor GUI, as it was required to reopen the table editor to see the changes. (Bug #65411, Bug #14137775)

  • On Mac OS X, MySQL Workbench would crash when changing database engines if a database included a table with uppercase characters. (Bug #65376, Bug #14117038)

  • The zoom feature (in or out) could cause a fatal error. (Bug #65247, Bug #14136870)

  • Deleting an EER diagram would cause MySQL Workbench to hang. (Bug #65174, Bug #14102990)

  • On Ubuntu 12.04, MySQL Workbench would not load. (Bug #64956, Bug #14180754)

  • The Copy Column Names to Clipboard option could crash MySQL Workbench. (Bug #64881, Bug #13970600)

  • Under certain conditions, adding a foreign key could generate invalid SQL code. (Bug #64539, Bug #13872284)

  • While editing an EER diagram, and click-dragging the mouse cursor, the cursor now remains in the same place it was originally clicked. (Bug #64487, Bug #13813199)

  • When altering a table with uppercase letters in the table name, MySQL Workbench would automatically convert the table name to lowercase. (Bug #64072, Bug #13639292)

  • If a view contains a row that is too long to be represented as a table column, it will now be substituted with an alias column in a placeholder table, similar to how mysqldump behaves. Before it could generate invalid SQL, and fail to synchronize the model. (Bug #63807, Bug #13538955)

  • Using File, Export, Forward Engineer SQL CREATE Script would remove delimiters statements if the Omit Schema Qualifier in Object Names option was selected. (Bug #63742, Bug #13520528)

  • MySQL Workbench would sometimes repeat a warning during a successful action that followed the action with the warning. (Bug #62454, Bug #13014873)

  • MySQL Workbench now uses the MySQL Server limit for maximum comment lengths while using the forward engineering wizard. Before it would truncate comments to 60 characters, which was a MySQL Server limit before version 5.5.3.

    From the MySQL Server 5.5.3 changelog: the maximum length of table comments was extended from 60 to 2048 characters. The maximum length of column comments was extended from 255 to 1024 characters. Index definitions now can include a comment of up to 1024 characters. (Bug #62207, Bug #12904170)

  • On Microsoft Windows, MySQL Workbench would ignore the system's font setting, but now uses it when MySQL Workbench is initialized. (Bug #62105, Bug #12872840)

  • Adding a trigger with the Alter Table, Trigger interface now warns the user if the inputted trigger statement was invalid. Before, MySQL Workbench would output "No changes to object were detected." if the SQL was valid, but without a CREATE TRIGGER statement. (Bug #61712, Bug #12908810)

  • Closing MySQL Workbench while editing SQL Scripts will now prompt the user to save the edits. (Bug #61037, Bug #62959, Bug #12546710, Bug #13344705)

  • MySQL Workbench now respects case-sensitivity when lower_case_table_names = 2. (Bug #60618, Bug #11926851)

  • Synchronizing a model would drop, and then re-add, indexes and foreign keys if the order of these indexes and foreign keys were different. This could happen because MySQL Workbench would add UNIQUE indexes in the order added by the user, whereas the MySQL Server puts them first. (Bug #60230, Bug #11829807)

  • A crash would occur if trigger code referred to tables in a schema different from the one where it is contained. (Bug #60041, Bug #13611382)

  • Loading large files (over 100MB) using File, Open SQL Script... failed to load the script, and throw an out of memory exception while halting operation.

    Now, MySQL Workbench warns users if a file exceeding 100MB is attempted to be loaded, and no longer crashes when running out of memory but instead reports that the file was unable to be loaded. (Bug #55312, Bug #60780, Bug #61363, Bug #64186, Bug #11762687, Bug #12339717, Bug #12627645, Bug #13790375)

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