MySQL Workbench

MySQL Workbench is a next-generation visual database design application that can be used to efficiently design, manage and document database schemata.

It is available as both open source and commercial editions. The Community (OSS) Edition is available from this page under the free software/open source GNU General Public License (commonly known as the "GPL").

Note: Now requires OS X 10.9 or later

Fixed

• Important Note: During normal operations, MySQL Workbench frequently and unexpectedly closed or became unresponsive.
• Compiler errors were resolved with GCC 6.2.1.
• Using the ->> operator in a valid SQL statement within a stored procedure returned the following error: The object's DDL statement contains syntax errors.
• The Columns tab of the table editor displayed an incorrect tooltip description for the G flag.
• For macOS, the table-partition model transposed column values leading to an incorrect CREATE TABLE statement.
• The migration script could not successfully convert UCS-2 strings to UTF-8 in a table when migrating the table from Microsoft SQL Server to MySQL Workbench.
• Database migration from Microsoft SQL Server 2000 emitted errors and stopped when the operation failed to locate the required schema list associated with the database version.
• A CASE statement with WHEN clauses in a stored procedure emitted syntax errors.
• On Windows, migrating a table with an empty string in a column of type ntext failed and displayed the "Could not successfully convert UCS-2 string to UTF-8 ..." error message.
• When migrating a table with a column of type nvarchar(max) from Microsoft SQL Server, MySQL Workbench found the record to be bigger than the server max_allowed_packet value and failed to copy the record to the server.
• The usage graph under InnoDB Status in the Performance Dashboard consistently underreported the actual usage of the InnoDB buffer pool as reported on the server. This fix implements a new formula to represent the InnoDB buffer pool.
• When closing a tab in the SQL Editor, the focus always returned to the first tab regardless of the number of tabs open. This fix returns focus to the preceding tab
• Index comments were improperly generated within the index section of an SQL script when using the Forward Engineer SQL Script wizard to create and export the script.