MySQL Workbench

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

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.
• The visual SQL editor reported a false error on the RENAME COLUMN clause of a valid statement.
• 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.
• 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.
• 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.
• 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.
• 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.
• The Ubuntu 19.04 distribution did not include MySQL Workbench support as expected.
• The reset operation for MySQL Enterprise Firewall rules produced an exception, instead of resetting the rules.
• The informational message shown when removing MySQL Enterprise Firewall was corrected.
• A blank MySQL Enterprise Firewall rule could be submitted, which generated an exception.
• MySQL Enterprise Firewall could not be enabled from MySQL Workbench after it was uninstalled and then reinstalled.
• Error messages within the Administration - Online Backup tab used incorrect characters to represent versions of MySQL Server.
• 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.
• 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.
• Unexpected cursor movement occurred within the query editor when using up and down arrow keys on computers running macOS 10.14 (Mojave).
• 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.
• 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.
• Connections made to 5.6 and 5.7 server instances used the utf8 character set, instead of utf8mb4.
• The opening and closing brackets were missing from the Type column output within the Administration - Server Logs tab.
• On computers running Windows, scrolling up and down with a pointer device was impaired.
• Test Connection functionality remained enabled for stored connections after they were deleted.
• 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.
• The PYC file associated with a plugin remained in the modules directory after the plugin was uninstalled.
• The MySQL Enterprise Firewall plugin was not recognized by MySQL Workbench when MySQL was installed from source.