Documentation Home
MySQL Workbench Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 1.0Mb
PDF (A4) - 1.0Mb

MySQL Workbench Release Notes  /  Changes in MySQL Workbench 5.2  /  Changes in MySQL Workbench 5.2.44 (2012-09-27)

Changes in MySQL Workbench 5.2.44 (2012-09-27)

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

This version adds native PostgreSQL and Sybase ASE support to the Database Migration Wizard.

Functionality Added or Changed

  • Added native migration support for PostgreSQL and Sybase ASE.

  • Updated the bundled MySQL Utilities to version 1.1.0, which includes the new mysqluc console.

Bugs Fixed

  • After right-clicking on a nonempty field in the SQL editor, and choosing Copy Row Content, pasting the row into an empty row (by right-clicking and choosing Paste Row) would not increment the row id when it was appropriate to do so. (Bug #14587186, Bug #66668)

  • When a table from Microsoft SQL Server was migrated to MySQL, TEXT columns were mapped to VARCHAR(16). They are now mapped to LONGTEXT because Microsoft SQL Server TEXT columns have a maximum length of 2^31 - 1. (Bug #14556732, Bug #66584)

  • The MySQL Workbench Data Export feature would fail to recognize tables that contained accented characters in the table's name. (Bug #14504342, Bug #66421)

  • The object browser would not update the column order after a table was altered. (Bug #14495629, Bug #66232)

  • On OS X systems with the Retina display, the mouse cursor would register incorrect mouse coordinates. (Bug #14396939, Bug #65607)

  • Entering the caret ("^") character inside the SQL editor, followed by any other character, could cause MySQL Workbench to hang. This was a Scintilla bug that is now fixed. (Bug #13930994, Bug #64848)

  • After choosing Alter Table, pressing Apply would cause MySQL Workbench to display "Preparing..." in the output panel, but it now displays "No changes detected." (Bug #13497239, Bug #63604)

  • When synchronizing a model to a database after changing a field definition from NOT NULL DEFAULT x to NULL DEFAULT NULL, the model synchronization would correctly generate the SQL. But after executing this SQL and resynchronizing, MySQL Workbench would report that the table needed to be updated. (Bug #12756728, Bug #61720)