MySQL Workbench

8.0.21.CE

8.0.21.CE

See all Versions

Functionality Added or Changed:

• A new check box was added to the dialog for resetting an expired password. When selected it indicates that the server version in use precedes MySQL 5.7

MySQL Workbench now supports the following MySQL 8.0.19 and 8.0.20 server language features:

• DROP CHECK, ALTER CONSTRAINT, and DROP CONSTRAINT in ALTER TABLE statements
• Locking clause for query expressions
• Table values constructor
• Short table select syntax
• New requirements for the CHANGE MASTER replication statement (row format, primary key check)
• Failed login attempts and password lock time in ALTER USER statements
• Format support for EXPLAIN ANALYZE statements

New and changed keywords:

• ARRAY
• FAILED_LOGIN_ATTEMPTS
• MASTER_COMPRESSION_ALGORITHM
• MASTER_TLS_CIPHERSUITES
• MASTER_ZSTD_COMPRESSION_LEVEL
• MEMBER
• OFF
• PASSWORD_LOCK_TIME
• PRIVILEGE_CHECKS_USER
• RANDOM
• REQUIRE_ROW_FORMAT
• REQUIRE_TABLE_PRIMARY_KEY_CHECK
• STREAM
• TIMESTAMP
• TIME

Bugs Fixed:

• MySQL Workbench Migration Wizard encountered type -154 (SQL_SS_TIME2) while copying Microsoft SQL Server tables, and it returned an error on the unhandled type. This fix adds the following new SQL data types to the wizard: SQL_SS_TIME2 (supported by MySQL) and SQL_SS_TIMESTAMPOFFSET (not supported)
• The TableRead, TableInsert, TableUpdate, and TableDelete events for each table touched by a query did not include complete information in the Audit Inspector
• Valid TABLE and VALUES statements were identified as having syntax errors in the SQL editor
• MySQL accounts created during the prerequisite setup using the Create MEB Account button were not granted sufficient privilege to schedule an online backup or to execute a full backup on Windows
• The Table Data Import Wizard returned an error when used to import a large JSON file, rather than loading the file
• Text selected in the SQL editor was blocked by the highlight color
• A change made to the CREATE statement to rename an existing stored procedure did not revise the corresponding name in the generated DROP PROCEDURE statement when the change was applied using the editor. This fix modifies the generated statement to no longer drop the original stored procedure after it is renamed
• On Windows, statements that do not generate a result set, such as INSERT or UPDATE statements, caused MySQL Workbench to close unexpectedly after the EXPLAIN operation was executed and then the Result Grid output type was selected
• Although the installation and file path were valid, MySQL Workbench did not find the ogr2ogr and ogrinfo files when loading spatial data
• A column created with NULL ON UPDATE CURRENT_TIMESTAMP(6) prevented the MySQL Table Editor from showing table information, such as indexes, views, foreign keys, and so on
• Memory use on a Windows host was excessive when a large result set was exported to a file, causing MySQL Workbench to become unresponsive
• Synchronizing a database that included a table with JSON fields to the data model produced new, separate tables for the JSON data, instead of updating the original table. In this instance, the target MySQL version set in the modeling preference, 5.6.30 by default, does not support the operation. This fix sets the default version to MySQL 8.0, but the value can be adjusted by selecting Preferences, Modeling, and then MySQL from the Edit menu
• The zoom-out button did not alter the zoom level of spatial data when viewed from a Linux host, unless the zoom level was reset to the outermost level first
• MySQL Workbench became unresponsive for several minutes after a server startup attempt was made on macOS hosts
• No errors or warnings were reported when scheduling a backup with MySQL Enterprise Backup, although the backup did not execute as scheduled
• A Sybase database migration with the ODBC (FreeTDS) connection method produced an exception when the connection was tested
• MySQL Workbench server administration could not acquire management access to Oracle Solaris. For a list of supported platforms, visit https://www.mysql.com/support/supportedplatforms/workbench.html
• On Linux, edits made to values in the result grid were lost when using the pointer device to move within the grid, rather than pressing the Enter or Tab key to change the focus
• Forward engineering a valid MySQL Workbench model was unsuccessful when the operation was performed using a MySQL 5.5 server instance
• On macOS, a query containing SELECT @@hostname returned the column header, but the query did not show any visible output unless the first row below the column header was selected
• After reverting changes made to triggers in a schema that had been saved and synchronized, MySQL Workbench was not able to locate any differences when the reverted schema was re-synchronized with the model
• A connection saved with MySQL Workbench Migration Wizard was no longer visible in the wizard after MySQL Workbench was upgraded to a later version. An attempt to save the connection again, using the same name, returned an error indicating that the original connection was preserved
• No connection could be made to the PostgreSQL database system when it was selected as the source in MySQL Workbench Migration Wizard on macOS