MySQL Forums
Forum List  »  Announcements

MySQL Workbench 8.0.18 has been released
Posted by: Nawaz Nazeer ahamed
Date: October 14, 2019 08:00AM

Dear MySQL users,

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

For the full list of changes in this revision, visit
http://dev.mysql.com/doc/relnotes/workbench/en/changes-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.18 (2019-10-14, General
Availability)

Functionality Added or Changed


     * MySQL Workbench now uses C++17.

     * An upgrade of the Scintilla library to the latest version
       (4.x) resolves a number of display problems observed on macOS
       Mojave.

     * RapidJSON, which is the parser used by other MySQL
       products, now replaces the native JSON solution.

     * Casmine, a custom behavior-driven development framework
       for unit and integration testing of MySQL Workbench code,
       replaces the TUT unit-test framework.

     * Previously, MySQL Workbench required access to the EPEL
       repository on enterprise Linux systems, such as Oracle Linux and
       Red Hat. Access to EPEL is no longer needed by MySQL Workbench
       for general use, but the repository is still required to use the
       spatial-data features in MySQL Workbench. The repository can be
       installed manually, if needed (see Installing Oracle Enterprise
       Linux and Similar
(https://dev.mysql.com/doc/workbench/en/wb-installing-linux.html#wb-installing-linux-installing-oel)).

Bugs Fixed


     * An inaccurate text message warned that tables, views,
       stored procedures, and functions could not be fetched when a
       MySQL account with limited administrative permissions on the
       server accessed a valid schema. (Bug #30105715, Bug #96357)

     * The visual SQL editor reported a false error on the
       RENAME COLUMN clause of a valid statement. (Bug #29938388,
       Bug #95901)

     * An error was generated when an attempt was made to add a
       new account or schema privileges after MySQL Enterprise Firewall
       was installed and enabled successfully. (Bug #29931969)

     * MySQL Workbench exits unexpectedly during an editing
       session of trigger code if the focus was shifted away from the
       Triggers tab and the trigger code contained an error.
       (Bug #29898662, Bug #95742)

     * The Firewall Rules tab was not shown as expected for any
       user account after the MySQL Enterprise Firewall plugin was
       installed and enabled successfully. Instead, MySQL Workbench had
       to be restarted to fully activate the feature when using either a
       local or remote-management connection. (Bug #29771365,
       Bug #29894485)

     * Partition details were not visible within the Partitions
       tab of Table Inspector when MySQL Workbench (on Windows) was
       connected to a MySQL server instance running on Linux.
       (Bug #29746607)

     * Underscore (_) characters in a schema name were converted
       to the equivalent wildcard characters when schema privileges were
       applied to a user account in MySQL Workbench. (Bug #29692955,
       Bug #95131)

     * The Ubuntu 19.04 distribution did not include MySQL
       Workbench support as expected. (Bug #29690500, Bug #95118)

     * The reset operation for MySQL Enterprise Firewall rules
       produced an exception, instead of resetting the rules.
       (Bug #29681550)

     * The informational message shown when removing MySQL
       Enterprise Firewall was corrected. (Bug #29681305)

     * A blank MySQL Enterprise Firewall rule could be
       submitted, which generated an exception. (Bug #29680813)

     * MySQL Enterprise Firewall could not be enabled from MySQL
       Workbench after it was uninstalled and then reinstalled.
       (Bug #29547778)

     * Error messages within the Administration - Online Backup
       tab used incorrect characters to represent versions of MySQL
       Server. (Bug #29455453)

     * On computers running MacOS, the up and down arrow keys,
       at times, reversed direction or moved to the next (or previous)
       query, instead of to the next (or previous) line. (Bug #29394563,
       Bug #94430)

     * Content within the input area of a Query tab did not
       scroll with the cursor when the cursor was moved beyond the
       current display range (up or down) using the keyboard on MacOS
       hosts. (Bug #29290375, Bug #94151)

     * Unexpected cursor movement occurred within the query
       editor when using up and down arrow keys on computers running
       macOS 10.14 (Mojave). (Bug #29049404, Bug #93576)

     * The model icons that represent relationship notations in
       an EER diagram, as well as the optional grid, were not visible in
       Dark Mode with macOS. (Bug #29049379, Bug #29049224)

     * On macOS, the code normally shown with View Source was
       not visible when Execution Plan was selected from the Result Grid
       side menu and Dark Mode was set. Similarly, code in the Workbench
       Scripting Shell was not visible.  (Bug #29024631, Bug #29127415)

     * Connections made to 5.6 and 5.7 server instances used the
       utf8 character set, instead of utf8mb4. (Bug #28912563,
       Bug #93136)

     * The opening and closing brackets were missing from the
       Type column output within the Administration - Server Logs tab.
       (Bug #28686449)

     * On computers running Windows, scrolling up and down with
       a pointer device was impaired. (Bug #28686322)

     * Test Connection functionality remained enabled for stored
       connections after they were deleted. (Bug #28672121)

     * On Windows, a query made on a table with exceptionally
       large column data, such as a BLOB column exceeding 5 MB, caused
       MySQL Workbench to stop working (client ran out of memory). On
       restart of the program, a locked file prevented additional
       queries until the computer was restarted. (Bug #27785104,
       Bug #89866)

     * The PYC file associated with a plugin remained in the
       modules directory after the plugin was uninstalled.
       (Bug #24522488)

     * The MySQL Enterprise Firewall plugin was not recognized
       by MySQL Workbench when MySQL was installed from source.
       (Bug #23617930)

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

Options: ReplyQuote


Subject
Views
Written By
Posted
MySQL Workbench 8.0.18 has been released
1305
October 14, 2019 08:00AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.