MySQL Workbench Manual  /  ...  /  New in MySQL Workbench 8.0 Release Series

1.1.1 New in MySQL Workbench 8.0 Release Series

This section summarizes how the MySQL Workbench 8.0 release series progressed with each minor release.

Character Set Changes

  • MySQL Workbench now uses utf8mb4 as the connection and client character set, replacing utf8mb3.

  • Support for the Chinese character set gb18030 was added.

SQL Query and Object Editors

  • 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.

  • 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.org by 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.

SQL Export Options

  • 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 9.4.1.1.1, “Creating a Schema”).

  • The OmitSchemas option replaces both the UseShortNames and OmitSchemata options to eliminate the schema name from table names when using the Python API to generate a schema from an .mwb file automatically.

MySQL Enterprise Backup (MEB)

SET PERSIST and SET PERSIST ONLY Functionality

  • 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.

Platform and Source Code Changes

  • 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.

Security Changes

  • libgnome-keyring was depreciated and replaced with libsecret in the MySQL Workbench 8.0.12 release on Linux platforms. The libsecret library 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_password authentication 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.2o (see https://www.openssl.org/news/openssl-1.0.2-notes.html).


User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
Sign Up Login You must be logged in to post a comment.