This section summarizes how the MySQL Workbench 8.0 release series progressed with each minor release.
Beginning with MySQL Workbench 8.0.17, the ANTLR4 grammar was updated to handle the language features of each supported MySQL server version from MySQL 5.6 to MySQL 8.0, including the following new language features in MySQL Server 8.0.17:
CHECKconstraints with enforcement.
ODBC table references now require the
OJkeyword (previously an identifier was allowed).
The equal sign (
=) operator for aliases is no longer allowed.
CHANGE MASTER supports
CREATE DATABASEstatement permits a default encryption to be specified.
Roles now support exception lists and
GRANT AS. Grant identifiers can be qualified with a schema name.
MEMBER OFis allowed in expressions.
AS ARRAYis allowed in
Passwords in user statements can now also be hexadecimal numbers.
Hexadecimal numbers are also allowed in many numeric expressions.
Minor items, such as, permit data types in number expressions, and reorganize keywords to lower conflicts in the server parser generation.
Removed support for MySQL 5.5 in the MySQL Workbench 8.0 release series. Minimum version now is MySQL 5.6.
If you still need to use MySQL Workbench on a MySQL 5.5 server, you can use MySQL Workbench 6.3, which is available from MySQL Product Archives.
MySQL Workbench now uses
utf8mb4as the connection and client character set, replacing
Support for the Chinese character set
As of MySQL Workbench 8.0.14, keyboard access was added to the home screen tab to enable navigation using Tab and Enter keys. In addition, the screen view now scrolls to display a selected item if the item was off-screen when highlighted with the Tab key.
On Windows and Linux hosts, the Application key and Ctrl+F10 now open a menu of commands (context menu) related to the selection.
Important change: MySQL model files last saved before MySQL Workbench 6.3 are no longer supported unless the models can be upgraded for use with the 6.3 release series.
Beginning with MySQL Workbench 8.0.16, the script editor highlights matching pairs of parentheses when one of the pair is selected.
SQL context help was enhanced to eliminate the requirement of having a valid MySQL connection to view the help topics and to improve the presentation of each help topic.
A new auto-completion engine was added for use with object editors (triggers, views, stored procedures, and functions) in the visual SQL editor and in models.
Geometry fields displayed in the result grid now include a context-menu item that opens the specific location value in a browser. The selected point opens in
openstreetmap.orgby default, but an alternative online service can be used (see Section 3.2.7, “Other Preferences” ).
Support for invisible indexes was added for use when the active server supports the feature and the index is neither a primary key index nor a unique column (see Invisible Indexes). A new option in the Indexes subtab of the table editor (for both the SQL and modeling editors) provides index visibility when it is selected.
A new SQL export option in the Forward Engineering SQL Script wizard sorts tables alphabetically in the generated script, rather than sorting tables according to foreign-key references by default (see Section 188.8.131.52.1, “Creating a Schema”).
OmitSchemasoption replaces both the
OmitSchemataoptions to eliminate the schema name from table names when using the Python API to generate a schema from an
Output from schema validation plugins for MySQL models now is shown in a single location and reorganized to provide informational, warning, and error messages by category. A new Validate tab also provides a simple way to reselect and rerun validation tests from the output area in the right side panel (see Section 9.2.3, “Schema Validation Plugins”).
MySQL Workbench now provides a simple way to enable or disable the persisted global system variable settings introduced in MySQL 8.0 (see SET Syntax for Variable Assignment). For variables that can be persisted, a new check box enables configuration changes at runtime that also persist across server restarts and applies the persisted value, if one exists. Persistent system variables can be reset (to not persist) individually or collectively. For additional information, see Persist System Variables.
Microsoft Visual Studio support was upgraded from Visual Studio 15 to Visual Studio 17 in the MySQL Workbench 8.0.16 release.
MySQL Workbench 8.0.14 (and higher) supports macOS 10.14 Mojave, including full compatibility with the Dark Mode color scheme.
Support for Microsoft Windows Server 2016 was added in the MySQL Workbench 8.0.11 release.
MySQL Workbench source code has been reformatted according to Google style.
libgnome-keyringwas depreciated and replaced with
libsecretin the MySQL Workbench 8.0.12 release on Linux platforms. The
libsecretlibrary provides enhanced cross-platform password storage and lookup.Important
Some users with existing stored passwords will be prompted to enter a password after upgrading.
SSH tunneling support was added to the MySQL Workbench Migration Wizard and also to the wbcopytables command-line utility for copying data.
Setting an encryption password is required to perform MySQL Enterprise Backup operations on encrypted tables (see Options Tab).
The SSH implementation based on Paramiko was replaced with the one based on libssh.
MySQL Workbench now supports the
caching_sha2_passwordauthentication plugin introduced in MySQL 8.0 (see Caching SHA-2 Pluggable Authentication).
All editions of MySQL Workbench and the bundled libraries were upgraded to use OpenSSL 1.0.2r (see https://www.openssl.org/news/openssl-1.0.2-notes.html).
As of MySQL Workbench 8.0.14, the following new functions are included in the Workbench GRT module:
Opens the selected EER diagram for use with the
Performs a PNG export of an EER diagram to the path provided without activating it.