In the Administrator tab of MySQL Workbench the Data Dump (Export/Import Data) feature now uses the --comments parameter when executing an import or export operation. (Bug#23002)

In the Manage Server Instances wizard, MySQL Workbench crashed if the New button was clicked. (Bug#48347)

On Ubuntu Linux, MySQL Workbench did not warn if a new model was to be saved as a file that already existed on the drive. (Bug#48345)

The Use compression protocol option was not working correctly when set in the Manage DB Connections wizard.

When the checbox Use compression protocol was selected in the Advanced tab of the Manage DB Connections wizard, the following error was generated when the connection was tested:

No bool value passed for CLIENT_COMPRESS

The same error occurred even if the Use compression protocol checkbox was subsequently cleared. (Bug#48202)

When editing a stored routine or trigger in the Table Editor, the cursor would relocate to the top of the editing window if a key was not pressed for a few seconds.

(Bug#48156)

Attempting to export the result of an SQL query to CSV using Query, Export Results... gave the error:

Failed to open template file: `/usr/share/mysql-workbench/modules/data/sqlide/CSV.tpl`

This occurred on a Fedora 11 AMD64 install, from RPM. The requested file was found in a different directory, /usr/share/mysql-workbench/sqlide/. The error did not occur after the file was moved to the required location. (Bug#48156)

In the Columns tab of the Table Editor, the tool tip for the AI column did not work. If the cursor was placed over the column no tool tip text was displayed. (Bug#48129)

If an EER Diagram tab was closed, it was not possible to reopen it by clicking on its icon on the model page. (Bug#47545)

In the GRT shell the help command, which is equivalent to ?, crashed when no arguments were specified. (Bug#47503)

The script generated by File, Export, Forward Engineer SQL CREATE Script dropped a schema if it existed and then recreated it. This resulted in loss of existing data. (Bug#47468)

When an attempt was made to add a database connection the following error was generated:

Test connect failed
Couldn't load library libmysqlclient_r.so: libmysqlclient_r.so: cannot open shared object
file: No such file or directory

This only happened on Linux. (Bug#47238, Bug#48507)

In the Inserts tab of the Table Editor, values entered for a BIT column were not saved. If values were entered and then the changes applied, the values in the BIT column disappeared. (Bug#47100)

When a model was loaded and an EER Diagram opened, the model navigator did not display the model correctly. (Bug#46970)

In the Table Editor, when trying to modify a column default value, errors occurred.

(Bug#46878)

In the Inserts tab of the Table Editor, if a string that contained spaces was added as an insert, then the string was truncated to the text before the first space. (Bug#46624)

In the Reverse Engineer Database wizard it was not possible to select only one table to reverse engineer, and then proceed to the next step. (Bug#45881)

When running a plugin that called a function such as the following, the document's status was set to “unsaved”, and an asterisk was displayed in the title bar, as soon as the file selection dialog opened. This occurred even for a new document, or an unmodified document.

function rfstest(obj)
  local path
  path = Workbench:requestFileSave("Caption", "SQL Files (*.sql)|*.sql")
end

(Bug#44813)

Forward Engineer SQL CREATE Script generated schema qualifiers for Stored Procedure names regardless of the setting of the Omit schemata qualifiers from output checkbox. This resulted in the generated script containing Stored Procedure names prefixed by the schema name. (Bug#43276)

In the Table Editor, the keyboard shortcuts such as Ctrl+X, Ctrl+V and Ctrl+C, affected the main document, rather than being confined to within the Table Editor. For example, if Ctrl+C was used to copy a column, this erroneously resulted in a duplicate table being created in the main model. (Bug#42626)

If a collation was set as the schema default, this was not correctly handled when the model was synchronized with a live database.

If a collation was set as a schema default, and then the model forward engineered to a database, then the collation was correctly set. If however, the model was then synchronized with the live database, MySQL Workbench attempted to alter the collations to utf8_general_ci. (Bug#38807)