Changes in MySQL Workbench 5.2.37 (2011-12-26)

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

• Functionality Added or Changed

• Bugs Fixed

Functionality Added or Changed

• The SQL editor now automatically fetches table data. (Bug #63590, Bug #13500202)

Bugs Fixed

• Under Server Administration, the location of the configuration file was not visible. It is now shown within the configuration file label. (Bug #14017264, Bug #65033)

• The SQL editor would open a table in read-only mode when opened from either the Edit Table Data link via the home screen, or if the schema tree was not expanded. (Bug #13466131)

• On OS X, the File, Open Recent feature would open the incorrect script. (Bug #13028666)

• Viewing the Server Logs on a MySQL server after it has been stopped, resulted in an unhandled exception. (Bug #12908134)

• Options unrelated to the SQL Editor would be available under the View menu while an SQL editor window was open. (Bug #11763150, Bug #55830)

• Pasting from the clipboard would not work in the hostname and related fields. Users are now able to paste values into these fields. (Bug #11753997, Bug #45528)

• Invalid SQL was generated when a schema name contained a dot. Table names are now enclosed in quotes. (Bug #63710, Bug #13500360)

• MySQL Workbench could freeze while importing a dump. (Bug #63669, Bug #13485795)

• Exporting a database that has a stored procedure, resulted in an unhandled exception. (Bug #63653, Bug #13476062)

• Generating a list of tables and views was slow, when compared to the previous MySQL Workbench version. (Bug #63633, Bug #13485667)

• Creating a foreign key using the Place a relationship using existing columns EER option would crash MySQL Workbench. (Bug #63629, Bug #13480328)

• Changing a schema name with routines present would prepend and append invalid delimiters. (Bug #63624, Bug #13470435)

• The field editor would hang when large text values were shown. (Bug #63606, Bug #13485779)

• MySQL Workbench now quotes table names in generated SQL queries, when the table name contains characters that would break the SQL statement. (Bug #63600, Bug #13497088)

• MySQL Workbench would generate an exception after editing and then closing a table tab within the EER diagram window. (Bug #63591, Bug #13463991)

• The SQL editor would not load under certain circumstances. The check for restoring split positions was corrected to solve this issue. (Bug #63582, Bug #13490891)

• The Help, Check for Updates feature did not function properly. (Bug #63534, Bug #13463399)

• The password prompt dialog is no longer the topmost window over all open applications on a system, but now it's only the topmost MySQL Workbench window. (Bug #63499, Bug #13496347)

• The user administration panel did not fit on systems using a 1024x768 screen resolution. (Bug #62341, Bug #12967541)

• On OS X, clicking Apply within the Alter Table dialogue on a table with foreign constraints would crash MySQL Workbench. (Bug #62042, Bug #12844307)

• MySQL Workbench required the Andale Mono font. (Bug #61782, Bug #12757325)

• MySQL Workbench would sometimes be unable to save changes that were only to comments. It used a hard limit, but now uses the MySQL Server limit for maximum comment lengths. For example, it would compare the first 60 characters of a table comment change, and generate an error if the change did not affect the first 60 characters.

  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 #61626, Bug #12694146)

• Database synchronization would sometimes confuse similar table and routine names. (Bug #61028, Bug #12656879)

• Case changes to ENUM values were not recognized by MySQL Workbench. (Bug #60478, Bug #11889204)

• The column header information is displayed as it is received from the server. (Bug #60237, Bug #11829800)

• Within the Database, Forward Engineer dialogue for a Model, the DROP Objects Before Each CREATE Object option was ignored if the Export MySQL Table Objects option was not selected. (Bug #59200, Bug #11766157)

• Altering the case of a table name caused an error, when that was the only change and the SQL Identifiers are Case Sensitive option was set to true. (Bug #58808, Bug #11765806)

• The export feature would sometimes fail when exporting tables with stored procedures, and with Dump Stored Procedures checked. And also having Export as Dump Project Folder selected would result in an unhandled exception. (Bug #57500, Bug #11764642)

• The Forward engineering feature now preserves case for schema names, even on case-insensitive systems. Before it would create lowercase variants of the schema names on these systems. (Bug #56237, Bug #11763520)

• The Forward engineer feature would sometimes create invalid SQL syntax for old MySQL Workbench files with deleted routines and roles. (Bug #53973, Bug #11761473)