This section documents all changes and bug fixes applied since the release of MySQL Workbench 5.1.12.
When using the Forward Engineer SQL Script wizard, the SQL Object Export Filter step displayed duplicate items. (Bug #45241)
When using the Generate Catalog Diff Report wizard, the Stored Connection information was not automatically populated when a previously defined Stored Connection was selected. (Bug #45234)
Adding Insert records for a table worked correctly. However, there was no way to remove the records once thefacility has been used to add them. (Bug #45233)
On OS X, using the Forward Engineer to Database, or Forward Engineer SQL Script wizards caused MySQL Workbench to generate this error message:
The application MySQLWorkbench quit unexpectedly after it was relaunched.
When defining a primary key with a user-defined data type, it was not possible to set the auto-increment (AI) attribute. Clicking the AI check box had no effect.
To circumvent this problem it was possible to temporarily change the data type of the column to a built-in data type such as
INT, set the AI attribute and then change the data type back to the desired user-defined data type. The model could then be saved. However, if this model was reopened and , , used to generate a script, MySQL Workbench would crash. (Bug #45165)
MySQL Workbench did not limit foreign key name length. This meant that an exported SQL script was invalid and MySQL Server generated an error on attempting to import it:
1059 - ER_TOO_LONG_IDENT
On OS X, if the mouse pointer was used to select an entity and then+ was pressed before the tooltip appeared, MySQL Workbench crashed when the delete was confirmed. (Bug #45042)
Foreign key names must be unique. However, MySQL Workbench default generated foreign key names were sometimes identical, causing Forward Engineer SQL CREATE Script to fail. (Bug #45027)
Synchronization of the model with an external database failed to report errors. This meant there was the possibility of an incomplete synchronization, without the developer being informed. (Bug #45024)
Changing a relationship's visibility had no effect.
If a relationship was right-clicked in the EER diagram, Relationship tab selected, the visibility radio buttons were displayed. However, if the visibility settings were changed there was no effect. (Bug #44988)selected, and then the
On Ubuntu Linux, MySQL Workbench crashed with a segmentation fault when an attempt was made to save the model. (Bug #44974)
On the Linux version of MySQL Workbench it was not possible to rename a layer by double-clicking it in the Layers window (which is typically docked to the right hand side of the screen).
A layer editor has now been added to the Linux version of MySQL Workbench. This can be activated by double-clicking the layer's title. (Bug #44972)
It was not possible to rename a table created using Add Table, by copying text into its text field. (Bug #44913)
In the Flags box, which is located in the Column Details panel in the Table Editor, the same flags were not listed as available for both the
ZEROFILLlisted, but these were not listed for the column if it was of type
INTEGER. Also, the AI check box was not selectable for columns defined as
INTEGER. (Bug #44872)
Using the Foreign Keys tab of the Table Editor, it was not possible to correctly create multiple foreign key relationships. (Bug #44701)
MySQL Workbench appeared not to display table rows in an EER diagram for tables that had more than 20 columns.
MySQL Workbench now includes the ability to manually resize the table, besides automatically limiting the number of columns to a user selectable value, by order of appearance, regardless of being key columns or not. (Bug #44675)
On Debian Linux (Lenny), after adding a second table and selecting AI on the first column element, MySQL Workbench generated a segmentation fault. (Bug #44612)
In the Workbench Preferences dialog, on the Diagram tab, in the Tables panel, the check boxes Show Column Types and Show Column Flags did not work correctly. Selecting or deselecting Show Column Types only had an effect when MySQL Workbench was restarted. Selecting Show Column Flags had no effect at all, and the flags were never displayed. (Bug #44586)
When in the Columns tab of the Table Editor, if an attempt was made to change a column data type to
INTEGER(n)this would have no effect and the column data type would remain unchanged. However, if
INT(n)was entered this was accepted and the data type changed accordingly. (Bug #44552)
When a new index was created in the Indexes tab for a table that already had indexes, the previously displayed index field remained selected. This caused concern that the newly created index would be on the wrong field. (Bug #44532)
The Forward Engineer SQL Script wizard did not permit the SQL script text to be copied using the keyboard shortcut. Only the mouse could be used to select and copy the text. (Bug #44531)
On Ubuntu Linux, the following MySQL Workbench menu items did not work:, and .
If those menu items were selected, these console messages were generated:
** Message: item_activated: 0xaa44bf0 -> 'builtin:wb.page_setup' ** Message: show_progress_becb not implemented ** Message: unhandled message 4: wb.print.setup finished in 0,00s ** Message: show_progress_becb not implemented create font Helvetica 0 0 11,000000 (200)** Message: item_activated: 0xa4c9800 -> 'plugin:wb.print.printPreview' ** Message: show_progress_becb not implemented ** (mysql-workbench-bin:11732): WARNING **: Could not open editor shared object '/usr/lib/mysql-workbench/plugins/' ** Message: unhandled message 4: wb.print.printPreview finished in 0,00s ** Message: show_progress_becb not implemented ** Message: item_activated: 0xa4cec08 -> 'plugin:wb.print.print' ** Message: show_progress_becb not implemented ** Message: unhandled message 4: wb.print.print finished in 0,00s ** Message: show_progress_becb not implemented create font Helvetica 0 0 11,000000 (300)
When a Routine Group was renamed, this was not immediately updated in the EER diagram. (Bug #44503)
Workbench:copyToClipboard()was used from within a plugin, only garbage characters were copied to the Windows clipboard. This affected the operation of plugins.
When a plugin attempted to output the string “abcdefghijklmnopqrstuvwxyz0123456789!§$%&/()=” a runtime exception was generated. (Bug #44461)
The Forward Engineer SQL Script wizard would write over an existing file without prompting the user for confirmation. (Bug #44437)
On OS X, an application window's red close button should contain a solid circle if the current document is unsaved. However, for MySQL Workbench this did not work correctly. Although the circle was initially shown, it was not displayed after subsequent edits to the model. (Bug #44435)
When attempting to delete an existing EER diagram, MySQL Workbench crashed.
The origin of the diagram seemed to have no bearing on whether the crash occurred because it happened both with diagrams created from reverse engineering and those created independently. (Bug #44407)
Deleting or cutting a Relation from an EER diagram crashed MySQL Workbench. (Bug #44340)
When Relations were deleted using the Foreign Keys tab, MySQL Workbench intermittently generated an exception:
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object args, Boolean synchronous) at System.Windows.Forms.Control.Invoke(Delegate method, Object args) at System.Windows.Forms.Control.Invoke(Delegate method) at MySQL.GUI.Workbench.Plugins.ObjectEditorPlugin.RefreshFormDataInvoke() at MySQL.Grt.DelegateSlot0<void\,void>.cpp_callback() at sigc.pointer_functor0<void>.()(pointer_functor0<void>* ) at sigc.adaptor_functor<sigc::pointer_functor0<void> >.()(adaptor_functor<sigc::pointer_functor0<void> >* ) at sigc.internal.slot_call0<sigc::pointer_functor0<void>,void>.call_it(slot_rep* rep) at MySQL.Grt.Db.TableEditorBE.remove_fk(NodeId fk) at MySQL.GUI.Workbench.Plugins.DbMysqlTableEditor.deleteSelectedFKsToolStripMenuItem_Click(Ob ject sender, EventArgs e) at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
When exiting MySQL Workbench with unsaved changes, you are given the choices, and . When was clicked, MySQL Workbench exited without saving, rather than returning to the application without making any changes.
This only happened when clicking the main application Close button, in the upper right corner. It did not happen if the application was exited by selecting, from the main menu. (Bug #44267)
Themenu item, which was normally available when right-clicking a table in MySQL Workbench, was not displayed. (Bug #44254)
If the order of columns was changed in the Columns tab, this was not reflected in the EER diagram. (Bug #44240)
In the table editor the
VARBINARYdata type was not listed in the list for columns. (Bug #44023)
In the table editor, when a column was added with a data type of
TIMESTAMP, and the default value of 0 entered, MySQL Workbench erroneously added quotation marks around the 0. Any generated SQL script therefore contained errors, and would subsequently fail. (Bug #44006)
The Forward Engineer SQL Script wizard did not emit table INSERT statements in the generated script when requested to do so. (Bug #43799, Bug #44385)
When synchronizing a model with a database, using the Synchronize Model with Database wizard, the data type translation resulted in errors. (Bug #42728)
Omit Schema Qualifiers did not omit schema for foreign keys.
When using Omit Schema Qualifiers check box, the schema for foreign keys were not omitted. (Bug #42328), , and selecting the
When editing a column's type in the Columns tab of the Table Editor, the list for selecting the data type displayed
BOOL. However, once that had been selected the data type was displayed as
Further, if a column data type was set by entering
INTEGERin the Datatype column, it then changed to
INTon pressing return. (Bug #41934)
MySQL Workbench frequently crashed with an unknown exception in Wb.h at line 1010.
This occurred while working on tables within EER diagrams on a design consisting of more than 190 tables and 20 EER diagrams. (Bug #41325)
Invisible characters in a reverse engineered script caused errors to be generated when the same script was forward engineered.
The problem was due to the reverse engineered script containing a mixture of \n, \r and \r\n line endings. These are now normalized to \n in the reverse engineering code. The validation process now also checks SQL code objects to ensure valid line endings. (Bug #41254)
When working in the Routines tab of the Routine Group editor, the Routine tab did not appear to save changes to routine code.
If code was copied from an external application into the Routine tab, then the model saved and MySQL Workbench exited, then on restarting MySQL Workbench, any changes to the routine code were lost. (Bug #40885)
When trying to synchronize a model to a database, tables defining some columns as
DOUBLEprevented the synchronization SQL script from working.
The SQL generated used the syntax
DOUBLE(256)which was rejected by MySQL Server 5.0.51a.
Editing the generated script manually to use just
DOUBLEworked. However, MySQL Workbench then assumed the target table was not correctly synchronized, and prompted the user accordingly. (Bug #40169)
When a relationship was fully visible in the EER diagram, if the user chose to have it drawn split, or hidden, MySQL Workbench behaved as expected. However, if the relationship was hidden, and the user chose to have it drawn split, or fully visible again, the relationship was not properly redrawn. The user had to move either of the tables involved in the relationship to have the relationship redrawn. (Bug #40015)
When editing a foreign key in the Foreign Keys tab of the Table Editor, and then removing the corresponding relationship from the EER Diagram canvas, the Foreign Keys tab remained open and populated, instead of being cleared and closed. (Bug #39478)
When tables with relationship connectors were dragged or copied from one EER diagram to another, the connectors were not always drawn. (Bug #38545)