MySQL Workbench Manual
This section documents all changes and bug fixes applied to MySQL Workbench since the release of MySQL Workbench 5.2.44.
This version adds support for MySQL Server 5.6.
Models: Copy, Cut, and Paste options were added to the context menu (right-click) of the Columns list in the models table editor. These options can be used between models. (Bug #13029519, Bug #62503)
The Control + / keyboard shortcut was added to comment/uncomment lines while editing SQL queries. (Bug #14803414, Bug #67002)
A button was added to the Server Status panel of the Server Administration window. It copies the query of the selected connection to the clipboard. (Bug #14799336, Bug #13571792, Bug #66728, Bug #63917)
An option was added to the SQL Editor and model
inserttabs. This import functionality parses a file with comma-separated values. (Bug #14079606, Bug #65252)The feature was added. It's similar to the existing feature, except this visual version generates a flowchart based on an
EXTENDEDEXPLAINstatement whereFORMAT = JSON. This feature requires MySQL Server 5.6.5 or above. (Bug #11765095, Bug #58021)
Linux: Right-dragging saved connections, models, and MySQL Server instances on the home screen could crash MySQL Workbench. (Bug #14812457)
Linux: Executing MySQL Workbench from the command-line would print
stdouttwice. (Bug #14565095, Bug #66590)OS X: The results window from executing an SQL query could be empty. A workaround was to resize the results window. (Bug #14520361, Bug #66446)
OS X: Closing MySQL Workbench after executing and making changes with the tool would not prompt the user with the save dialog. (Bug #14456136)
OS X: On OS X, the default column name and column type model preferences did not function. Note that this feature does not function on Linux. (Bug #14399236, Bug #66090)
OS X: The ability to select multiple columns in the models table editor did not function on OS X. It is now possible to use Shift, Command, and mouse dragging. (Bug #11766291, Bug #59372)
Microsoft Windows; Models: After opening and then closing a model file from the file manager, attempts to open a different model file failed to load the model. (Bug #14791573, Bug #67312)
Microsoft Windows; Models: Model files (*.mwb) would not load MySQL Workbench after being double-clicked in
Windows Explorer. (Bug #14521111)Microsoft Windows: Pressing Control + A in the table editor on a table field would select all table entities instead of the text in the field. (Bug #15884658, Bug #67610)
Microsoft Windows: Clicking on the Schema and Schema Objects column headers within Server Administration, Data Export would properly sort in
descendingorder, but would not sort inascendingorder when clicked again. (Bug #15849616, Bug #67518)Microsoft Windows: The Enter key would not create newlines within the table column comment dialogue. (Bug #14829617, Bug #67320)
Microsoft Windows: Renaming an EER Diagram would crash MySQL Workbench. (Bug #14799722, Bug #66818)
Microsoft Windows: The button would not display the results in the
Explaintab. (Bug #14702591, Bug #67059)Microsoft Windows: Right-clicking on a database name in the schema browser and choosing would add a strikethrough to the chosen database name. (Bug #14663690, Bug #66930)
Microsoft Windows: Queries surrounded by parenthesis would not display results in the view tab. (Bug #14651969, Bug #66887)
Microsoft Windows: A model failed to load when opened from the Microsoft Windows 7 taskbar if a different model was already open. (Bug #14621880, Bug #66799)
-
Microsoft Windows: The Id and Time columns within the Server Administration, Server Status, Connections panel would not sort properly, as they were sorted as ASCII values instead of numerically.
Additionally, miscellaneous sorting improvements were implemented. (Bug #14612413, Bug #15953190, Bug #66768, Bug #67786)
Microsoft Windows: After using the schema search filter in the object browser, right-clicking on a filtered schema would generate a context menu with invalid options. (Bug #14521006, Bug #66346)
Microsoft Windows: Control + H did not invoke the replacement function. (Bug #14520920, Bug #66422)
Microsoft Windows: Find and Replace would not function properly while using '_' as a replacement character. (Bug #14499088, Bug #66390)
Microsoft Windows: The Explain Current Statement option would not function. A workaround is to manually prepend
EXPLAINto your query. (Bug #14483518, Bug #66157)Microsoft Windows: Control + A would not always select data from cells in the query results tab. (Bug #13891109, Bug #64723)
Microsoft Windows: The default plugin directory in the configuration tab was set as a Linux style path such as
"/usr/", but it is now based on the OS awareBASEDIRvalue. (Bug #11764440, Bug #57271)MySQL Server 5.6: The partition count definition was limited to 1-10 as a drop-down selector in MySQL Workbench. This option is now a text field, which accommodates the 8192 partition limit in MySQL Server 5.6. (Bug #14786614, Bug #67166)
MySQL Server 5.6: The SQL Editor would emit invalid syntax errors with MySQL 5.6 queries. For example,
GET DIAGNOSTICSqueries would return "syntax error, unexpected IDENT_QUOTED, expecting ':'". (Bug #14786599, Bug #14786604, Bug #14786615, Bug #67163, Bug #67164, Bug #67168)MySQL Server 5.6: MySQL Workbench would not allow passwords to be created or changed for user accounts that utilize the SHA-256 Authentication Plugin, which exists as of MySQL Server 5.6.6. (Bug #14786567, Bug #14786558, Bug #67158, Bug #67154)
MySQL Server 5.6: The MySQL 5.6
ALTER USER ... PASSWORD EXPIREoption is now supported. An expired password indicator, and an button to expire the current password, were added. (Bug #14786564, Bug #67157)MySQL Server 5.6: The SHA-256 Authentication Plugin is now supported. (Bug #14786561, Bug #67155)
MySQL Server 5.6: MySQL Workbench now supports MySQL Server 5.6 configuration options. (Bug #14786556, Bug #67153)
-
MySQL Server 5.6: MySQL Workbench would alter the
mysql.*system tables for tasks such as account management, instead of using the corresponding account manipulation statements. This would conflict with GTID usage as of MySQL Server 5.6.This could have also caused a user password to be reset after modifying the user privileges. (Bug #14786531, Bug #14725272, Bug #67150, Bug #67100)
MySQL Server 5.6: A
DDLrelated parsing error would be generated while attempting to update an existing routine that contained aDateTimevariable type with precision. This feature is specific to MySQL Server 5.6. (Bug #14684874, Bug #14545075)MySQL Server 5.6: Creating a standard user with MySQL Server 5.6 would sometimes fail, and emit an error that referred to an unknown
mysql_native_passwordplugin. (Bug #14574998, Bug #66638)MySQL Server 5.6: All MySQL Server 5.6 system variables were listed under the Other tab instead of their proper location. For example,
gtid_doneis now listed under the Replication tab. (Bug #67170, Bug #14786569)MySQL Server 5.6: The MySQL Workbench UI now supports the extended
TIMESTAMPandDATETIMEfeatures that MySQL Server 5.6 offers. Both the initial and on-update values can now be defined for these types, and the fractional-second granularity is also now supported. (Bug #67165, Bug #67169, Bug #14786605, Bug #14786616)MySQL Server 5.6: The creation of a username and password will now utilize the Password Validation Plugin in MySQL 5.6. This option is available within the Server Administration section, under the Security Options tab. (Bug #67152, Bug #67161, Bug #14786551, Bug #14786626)
MySQL Server 5.6: Creating a standard MySQL Server 5.6 user account in MySQL Workbench failed, and emit an error related to the
msyql_native_authplugin. (Bug #67151, Bug #14786542)Migration: Migrating a Microsoft SQL Server database failed if
nvarchar(max)was used. These are now converted toLONGTEXT. (Bug #14780416, Bug #67289)Migration: From within the Manual Editing section of the database migration procedure, viewing Migration Problems after All Objects would continue to display information from All Objects. (Bug #14761792, Bug #67229)
Migration: Migrating from MySQL Server 5.0 to MySQL Server 5.6 could fail. The migration tool now supports MySQL Server 4.1 and above as the source database. MySQL Server 5.1 and above are supported as the target database. (Bug #14647426, Bug #66861)
Models: Model notes could not be saved. The button is available again. (Bug #14813462, Bug #67211)
Models: Switching from a table column tab to a different tab, and then back to the column tab, would add an empty column named "
tablenamecol". This empty column would be added to the table unless Escape was pressed. (Bug #14768685, Bug #67235)Models: Synchronizing a model with a database could crash MySQL Workbench by causing a segmentation fault. (Bug #14588524, Bug #66707)
Models: While executing the Synchronize Model with Database wizard, invalid trigger related errors could be emitted even though the definitions were correct. (Bug #14498358, Bug #65982)
Models: Forward Engineering a model with users and roles could generate invalid SQL, because the username was not escaped within the generated
GRANTstatements. (Bug #14396930, Bug #66070)Models: The , , feature failed to function. (Bug #13548113, Bug #63878)
Models: Sometimes a modified stored procedure would not be flagged as modified while synchronizing a model. (Bug #13364922, Bug #62595)
Models: The ability to open model files from older versions of MySQL Workbench has been improved. (Bug #12747012, Bug #61703)
Models: When editing an EER diagram, the context menu option follows behavior by also deleting the schema object. It will now only remove it from the EER canvas. And a new option was added that also only removes an object from the EER canvas. (Bug #11761492, Bug #53994)
Models: Pressing in either the Create EER Model from Existing Database or Create EER Model from SQL Script dialogs would still open a Model tab. (Bug #11757140, Bug #49145)
Under certain circumstances, comments could interfere with the execution of SQL statements. (Bug #15960066, Bug #67747)
Clearing the output window while a query was running could cause MySQL Workbench to crash after the query finished. (Bug #15891884, Bug #67618)
Saving script files did not function properly with the clipboard. Content pasted from the clipboard was not saved. (Bug #15837775, Bug #67462)
Having
sql_modeset toPAD_CHAR_TO_FULL_LENGTHcauses the routine functionality to fail, as MySQL Workbench is not designed for this setting. A connection specificsql_modeoption was added, and it can be set from the Advanced tab in the Connection Editor. It defaults to "". (Bug #14845656)The following scenario would crash workbench: open a table, insert a new row of data, close the table, open a different table via double-click, then press . (Bug #14829570, Bug #67237)
MySQL Workbench failed to interpret C-style comments, such as
/*! MySQL-specific code */. For more information about comment usage in MySQL, see Comments. (Bug #14807602, Bug #67203)Opening a connection using Open connection to Start Querying from the MySQL Workbench home screen could crash MySQL Workbench. (Bug #14803527, Bug #67074)
Added
DbMySQLQuery->affectedRows, fixedMySQLResult->firstRow, and added a Splitter control to the Python binding for mforms. (Bug #14799403, Bug #66804)Procedures were always included in the exported SQL, even if excluded via a filter or configuration setting. (Bug #14758896, Bug #66790)
An error tooltip would sometimes fail to be displayed while hovering the mouse pointer over an error marker in the SQL editor. (Bug #14705012, Bug #67067)
The Select Objects to Forward Engineer filter was ignored while executing Forward Engineer to Database. All tables were exported. (Bug #14696609, Bug #67031)
A crash could occur after switching tables in the EER Diagram tab while the Privileges was open, or while adding roles to the active table. (Bug #14645542, Bug #66869)
A model could not be synchronized if a field contained a comment with a single quote. (Bug #14582241, Bug #66680)
An exception would be generated when executing Forward Engineer without a MySQL Server connection. (Bug #14574987, Bug #66648)
Lower level changes, such as a newly created
TRIGGER, would not be visible after the object browser was refreshed. (Bug #14551801, Bug #66549)The non-functional comments box was removed from the schema editor. (Bug #14548126, Bug #66553)
The bundled
ChangeLoglisting was outdated. (Bug #14547966, Bug #66528)In the MySQL Workbench Scripting Shell, an exception is now thrown while attempting to use
input()or read fromstdin. (Bug #14520741, Bug #66452)The mouse scroll would not function while viewing the Options File in the Server Administration panel. (Bug #14388344)
Unlike the Server Administration panel (since 5.2.35), the SQL Editor did not support syntax that utilized the authentication plugins. (Bug #14356470)
The Server Access Management interface would not allow a password to be set as an empty string. (Bug #14278189, Bug #65739)
The Limit Connectivity to Hosts Matching option did not allow an IP with a Subnet Mask because "/" was considered an invalid character. (Bug #14207793, Bug #65583)
Having multiple connections with TCP/IP over SSH could cause MySQL Workbench to not connect when exceeding
MaxAuthTries. This may happen if an encryption type is unknown. The bundledparamikolibrary (on OS X, and Windows) was updated to version 1.7.7.1, which helps solve this problem, as it adds known support for OpenSSL keys. (Bug #13919914, Bug #64802)Multiple instances of MySQL Workbench will no longer open the same database model file. Doing so caused problems with features such as auto save and file locking. (Bug #13864687, Bug #64639)
An SSL connection required a client certificate. (Bug #13851229, Bug #61266)
A new General, SQL Editor option was added. Enabling Create new tabs as Query tabs instead of File (disabled by default) causes new SQL Editor tabs to default as Query tabs instead of SQL File tabs. File tabs include additional options, and prompt to be saved when the tab closed. (Bug #13492434, Bug #14541178, Bug #62929, Bug #66541)
Changing a foreign key column to be nullable now deselects the mandatory check box. If all foreign key columns are set to
NOT NULL, then the mandatory check box value will be selected. (Bug #13252655, Bug #62737)The
Start Command Line Clientfeature would fail to connect with SSH connections. (Bug #12612343, Bug #61325)A Refresh Rate option was added to the Server Administration, Server Status window. The refresh rate defaults to "Don't Refresh" and includes options ranging from 0.5 to 30 seconds. (Bug #11926869, Bug #60546)
It was not possible to sort schemas for exporting. (Bug #11926862, Bug #60566)
Changes to the
DEFINERclause were not detected by the wizard when altering this clause was the only change. (Bug #11829867, Bug #60164)Importing a saved connection that used an SSH tunnel would throw an exception, and fail to import the connection. (Bug #11765909, Bug #58922)
Attempting to open MySQL Doc Library while it was already opened would generate an error. (Bug #11763691, Bug #56432)
When foreign keys are added, existing indexes are now used instead of always creating new indexes. (Bug #11760834, Bug #53277)
Opening a model from a newer version of MySQL Workbench could generate an error dialog that was hidden behind the splash screen. This made it difficult to close the splash screen, which meant MySQL Workbench could not be used. A workaround was to pass in the
-nologooption at startup. (Bug #11754043, Bug #45582)The
ALTER ROUTINEfunctionality would not detect stored procedure changes when only the case changed. This check was case-insensitive. (Bug #65277, Bug #14136994)