Dear MySQL users,
The MySQL developer tools team announces 6.3.8 as our GA release for
MySQL Workbench 6.3.
For the full list of changes in this revision, visit
http://dev.mysql.com/doc/relnotes/workbench/en/changes-6-3.html
For discussion, join the MySQL Workbench Forums:
http://forums.mysql.com/index.php?152
Download MySQL Workbench 6.3.8 GA now, for Windows, Mac OS X 10.9+,
Oracle Linux 6 and 7, Fedora 23 and Fedora 24, Ubuntu 16.04
or sources, from:
http://dev.mysql.com/downloads/tools/workbench/
Enjoy!
Changes in MySQL Workbench 6.3.8
Bugs Fixed
* Important Note: During normal operations, MySQL Workbench
frequently and unexpectedly closed or became
unresponsive. (Bug #24571739, Bug #82778)
* Compiler errors were resolved with GCC 6.2.1. Thanks to
Christian Hesse for the patch. (Bug #24842267, Bug
#83372)
* Using the ->> operator in a valid SQL statement within a
stored procedure returned the following error: The
object's DDL statement contains syntax errors. (Bug
#24693021, Bug #83043)
* The Columns tab of the table editor displayed an
incorrect tooltip description for the G flag. (Bug
#24558804)
* For macOS, the table-partition model transposed column
values leading to an incorrect CREATE TABLE statement.
Thanks to Kit Yam Tse for the patch. (Bug #24517322, Bug
#82716)
* 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. (Bug #23751080)
* 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. (Bug #23747299, Bug #82069)
* A CASE statement with WHEN clauses in a stored procedure
emitted syntax errors. (Bug #23746795, Bug #82114)
* 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. (Bug #23630604, Bug #81967)
* 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. (Bug #23623191, Bug #81944)
* 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. (Bug #23584042, Bug #81837)
* 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. (Bug
#19896276, Bug #74530)
On behalf of the MySQL Workbench and the MySQL/ORACLE RE Team