MySQL Workbench 8.0.19 has been released

[Nawaz Nazeer ahamed]

Dear MySQL users,

The MySQL developer tools team announces 8.0.19 as our General Availability
(GA) for MySQL Workbench 8.0.

For the full list of changes in this revision, visit
https://dev.mysql.com/doc/relnotes/workbench/en/news-8-0.html

For discussion, join the MySQL Workbench Forums:
http://forums.mysql.com/index.php?152

The release is now available in source and binary form for a number of
platforms from our download pages at:

http://dev.mysql.com/downloads/tools/workbench/

Enjoy!

Changes in MySQL Workbench 8.0.19 (2020-01-13, General Availability)

Functionality Added or Changed

     * Important Note:
       MySQL Workbench 8.0.19 is unable to open a new connection to
       MySQL Server from the home screen if the server is not started
       and you cannot start a server by using the Workbench
       Administration feature. Administrative and SQL editing tasks
       require an online server for the duration of this issue. Feature
       tasks that you performed with an offline server in previous
       releases now return an error message indicating that the server
       is unreachable.  This issue is limited to MySQL Workbench 8.0.19.
       Thank you for your patience.
       Workaround: Start MySQL Server independently before opening the
       Administration and SQL Query tabs in MySQL Workbench. On Linux,
       you can replace the MySQL Connector/C++ 8.0.19 library with the
       8.0.18 library.

     * A new context menu item now copies the headers and rows
       of queried data with tabs as separators, making it convenient to
       copy and paste query results into Excel.  Thanks to Raj Rao for
       the patch. (Bug #30568824, Bug #97712)

     * The following MySQL server language features are now
       supported: value references in INSERT statements, new options
       (TLS version, cipher suite, compression, and privilege check) in
       CHANGE MASTER TO replication statements, random passwords in
       CREATE USER and ALTER USER statements, EXPLAIN ANALYZE, and
       binary collation names.

     * Context help for the keywords and functions in SQL
       queries now includes updated syntax and usage information.

Bugs Fixed


     * When attempting to export MySQL 5.7 data using MySQL
       Workbench 8.0, the server returned an error indicating that
       INFORMATION_SCHEMA.COLUMN_STATISTICS was an unknown table.
       Consistent parameter use with mysqldump now skips the table as
       expected. (Bug #30515899, Bug #97520)

     * The SQL editor applied syntax-error highlighting to the
       EXPLAIN keyword in a valid statement prefixed with EXPLAIN
       ANALYZE, but the statement executed as expected.  (Bug #30478023,
       Bug #97416)

     * A syntax error was generated for valid ANALYZE TABLE
       statements with either the UPDATE HISTOGRAM or DROP HISTOGRAM
       clause. (Bug #30449796, Bug #97281)

     * Storage engines not supported by MySQL were listed as
       possible engines that could be selected for tables.  Unsupported
       storage engines now are removed from the suggestion list.
       (Bug #30338754, Bug #96968)

     * An existing stored connection could not be replaced with
       a new connection having the same name when the attempt was made
       from the Source Selection step of the MySQL Workbench Migration
       Wizard. (Bug #30269513)

     * On macOS, the Cancel and Export buttons in the Export
       Recordset context window (for SQL INSERT statements) were mostly
       hidden. (Bug #30244028, Bug #96689)

     * If the ls command produced an error message together with
       a list of files, no audit log for the error appeared in the
       Enterprise MySQL Audit Log Inspector. (Bug #30135391)

     * An original SQL Server record (for example, 1020.6) was
       copied inaccurately to the corresponding MySQL column (1020.0)
       when migrated using the DECIMAL data type.  Similarly, data
       migrated using the NUMERIC type generated a type-conversion
       error. Now, both decimal and numeric values are stored as DECIMAL
       types to fix the resolution of the decimal value or to fix the
       type conversion. (Bug #30062094, Bug #96230, Bug #30263415,
       Bug #96744)

     * The uniqueidentifier data type in a SQL Server source
       table was interpreted during migration as type VARCHAR(64) UNIQUE
       in the MySQL target column, instead of a VARCHAR column to
       represent a GUID (UUID) that is not unique. (Bug #29355468,
       Bug #94066)

     * The relationship arrows within an EER diagram were not
       visible when the Dark Mode theme was enabled on a macOS host and
       the diagram was exported as a single page PDF file. This fix
       disables the theme in models to prevent conflicts with the colors
       assigned by the model editor.  (Bug #29307893, Bug #94174)

     * An empty file list was shown when the audit_log_file
       value was set to any location other than the MySQL server data
       directory. (Bug #22673089)

On Behalf of Oracle/MySQL Release Engineering Team,
Nawaz Nazeer Ahamed