First Beta release of 5.2. This section documents all changes and bug fixes applied since the release of MySQL Workbench 5.2.7.
When a table was edited in the EER Diagram view, and Control+S was pressed to save the model, the model file was not saved. (Bug #48682)
If an model object, such as a schema or table, was deleted or its creation was undone using the undo feature, while the object editor was open, a crash occurred if the editor was then subsequently closed. (Bug #48664)
When running MySQL Workbench, this error occurred when an attempt was made to change the Windows screen resolution:
cairo error: out of memory
MySQL Workbench did not start correctly. At startup it generated this error:
Microsoft Visual C++ Runtime Library Runtime Error! Program C:\Pro... This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
Once a default value had been set for a column in the Table Editor, it was not possible to remove it. (Bug #47085)
The View text editor was overly aggressive in trimming excess whitespace from View definitions. If there was some hesitation after the user entered one or more spaces, the editor would trim whitespace back to the last non-space character entered. (Bug #46894)
In the EER Diagram view, the auto-resizing of tables did not work correctly, tables were too small to permit all columns to be visible. (Bug #46806)
When using the Fedora 10 RPM installation packages on Fedora 11, opening a database connection produced this error:
Cannot Connect to Database Server Connection 'antonia' could not be established: Database driver: Failed to open library '/usr/lib/mysql-workbench/mysqlcppconn.so'. Check settings.
The MySQL Workbench libraries were installed in
/usr/lib/. (Bug #46428)
In the Manage DB Connections dialog, the text fields Username, Password, and Default Schema accepted text, but as the text was being entered only the top half of the characters entered displayed. However, once the text had been submitted, the characters were displayed correctly. (Bug #45106)
Printing of an EER Diagram did not work correctly if a table vertically spanned multiple pages. In this case pages would be printed up to and including the page that contained the first part of the table that spanned multiple pages, but the pages containing the remaining parts of the table would not be printed. This problem typically occurred when a table had more fields than could comfortably fit on a single page. (Bug #33919)