MySQL Workbench 6.1.6 GA has been released

[Balasubramanian Kandasamy]

 
Dear MySQL users,

The MySQL developer tools team announces 6.1.6 as our GA release for
MySQL Workbench 6.1.

MySQL Workbench 6.1.6 is a maintenance release and contains over 30
fixes and minor enhancements made since the original GA release.

MySQL Workbench 6.1

Introducing over 30 new features, this version has many significant
enhancements focusing on real-time performance assessment and analysis
from the SQL statement level to server internals and file IO. You can
see this from additions to the SQL Editor as well as new dashboard
visualization and reporting that take advantage of MySQL Server 5.6
and 5.7 Performance Schema, and enhancements to the MySQL Explain Plans.

Additionally Workbench 6.1 is leveraging work from various teammates in
MySQL Engineering by introducing a schema called "SYS" that provides
simplified views on Performance Schema, Information Schema, and other
areas.
Special thanks to the server optimizer team, server runtime team, and Mark
Leith.  For Oracle DBAs MySQL SYS is similar to the V$ catalog views, and
MSSQL folks its like DMVs (Dynamic Management Views).

MySQL Workbench 6.1 includes:

* Improved drag and drop support in the Home screen and SQL Editor
* Visual Explain 2. The Visual Explain feature was revamped and is now
easier to read and interpret. You can also get the traditional tabular
explain output from within the same interface.
* Performance Dashboard. A graphical representation of some key statistics
from the server status, gives you a bird's eye view of the status of key
server subsystems.
* For advanced users, Performance Schema Instrumentation. A GUI for
configuring the Performance Schema in detail, for advanced users.
* Performance Schema based reporting. Gives insight into the operation
of the server through many high-level reports.
* New query result view. Get more information about queries you execute,
such as information about the fields in your result set and key performance
statistics from your query (timing, index usage, number of rows scanned,
joins etc).
* Form Editor for resultsets. In addition to the result grid, you can now
edit records row by row in a form style editor.
* Table Inspector. Similar to the Schema Inspector, view detailed
information from tables. A streamlined interface for creating indexes is
also included.
* Support for the Windows accessibility API and Windows high contrast
color schemes. A new high contrast theme has been introduced.
* And more.

More than 60 enhancement requests and bugs reported by users have also been
addressed, providing performance, usability and stability improvements
across the board.

For the full list of bugs fixed in this revision, visit
http://dev.mysql.com/doc/relnotes/workbench/en/changes-6-1.html

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

Download MySQL Workbench 6.1.6 GA now, for Windows, Mac OS X 10.6+, Oracle
Linux 6, Fedora 19, Fedora 20, Ubuntu 12.04 and Ubuntu 13.10 or sources,
from:

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

In Windows, you can also use the integrated MySQL Installer to update
MySQL Workbench and other MySQL products.

Quick links:
-http://mysqlworkbench.org/
- Download:http://dev.mysql.com/downloads/tools/workbench/
- Bugs:http://bugs.mysql.com
- Forums:http://forums.mysql.com/index.php?151

Enjoy!

Changes in MySQL Workbench 6.1.6 (2014-05-16)

   Functionality Added or Changed

     * MySQL Workbench now shows a SSH fingerprint dialog box when
       connecting to an SSH server, to notify you when the
       fingerprint does not correspond to the fingerprint stored (in
       known_hosts) for that particular server. (Bug #11765158, Bug
       #58091)

   Bugs Fixed

     * MySQL Workbench could crash with a MySQL connection that was
       defined with an unprivileged MySQL user. (Bug #18704357, Bug
       #72350)

     * On Mac OS X, the code completion tooltip could be displayed on
       top of a non-Workbench application. (Bug #18593798, Bug
       #72344)

     * The Show in Editor functionality from the Client Connections
       context-menu would not function (the option was grayed out).
       (Bug #18598559, Bug #72349)

     * The following scenario generated a segmentation fault in the
       EER diagram editor: Double-click a table with a FK,
       double-click a table with a FK, select the Foreign Keys tab,
       and to generate the "Index out of range" error and segfault,
       either double-click an existing table or create a new table.
       (Bug #18632808, Bug #72329)

     * The Don't create table placeholder for views option of the
       Forward Engineer SQL Create Script wizard did not function.
       (Bug #18614177, Bug #72366)

     * Closing the Stored Procedure Editor after changing a stored
       procedure (and clicking Apply) would emit an "Object reference
       not set to an instance of an object." error. (Bug #18591542,
       Bug #72328)

     * When generating a Visual Explain report, a group operation
       would cause the generated JSON output to contain a node error.
       (Bug #18534644, Bug #72180)

     * Subsequent executions of Query, Execute (All or Selection) to
       Text would cause the result's tab title from the previous
       execution to turn blank. (Bug #18516486, Bug #72232)

     * In the EER diagram editor, tooltips are now hidden when mouse
       movements or clicks are registered, and they are also hidden
       when switching applications. (Bug #18536932, Bug #72257)

     * With the Collect Resultset Field Metadata disabled, the Form
       Editor results view was blank. It now displays a message
       asking the user to enable the required Query, Collect
       Resultset Field Metadata preference. (Bug #18516369, Bug
       #72233)

     * Altering (adding values to) an ENUM column potentially caused
       MySQL Workbench to crash. (Bug #18530674, Bug #72267)

     * The Query Stats panel contained the string "sigle" instead of
       the word "single." (Bug #18516611, Bug #72228)

     * Clicking a column header in an SQL result view sorts rows in
       ascending order, but clicking the column header a second time
       would not sort the rows in descending order. (Bug #18517317,
       Bug #72226)

     * Executing the Select Objects to Forward Engineer step in the
       Forward Engineering wizard would crash MySQL Workbench each
       time the wizard is executed after the first time. In other
       words, the wizard would only execute every step with success
       during its initial (first) execution. (Bug #18526002, Bug
       #72251)

     * Executing a Visual Explain would sometimes generate an error
       with the text "Error calling Python module function
       SQLIDEQueryAnalysis.visualExplain". (Bug #18509791, Bug
       #72216)

     * After clicking Apply to save changes to a result set in the
       SQL editor, the executed SQL statement was no longer being
       displayed. (Bug #18490695, Bug #72155)

     * Executing Backup Restore with a MySQL user lacking the proper
       permissions would generate an unhandled exception. (Bug
       #18490779)

     * The PERFORMANCE schema navigator tab was disabled for MySQL
       server 5.5 (and below) MySQL connections, as the system
       requires a MySQL server 5.6 (and above) connection. Attempting
       a MySQL server 5.5 would report an error about a missing
       sys_55.sql configuration file. (Bug #18502244, Bug #72201)

     * Rapidly clicking Execute in a SQL session too frequently
       sometimes caused MySQL Workbench to crash. (Bug #18491041)

     * On Mac OS X, the background banner for the 6.1 installer (DMG
       file) incorrectly displayed 6.0. (Bug #18491018)

     * On Microsoft Windows, the Management, Client Connections, View
       Thread Stack feature failed to function. (Bug #18490766)

     * Mixed case and lower cased triggers were not properly
       displayed in the Alter Table tab, causing them to not be
       visible or editable. (Bug #18436881, Bug #71868)

     * A MySQL connection that was created without a defined username
       and password would fail to open, despite prompting for the
       username and password. (Bug #18436002)

     * On Mac OS X, and after adding a backtick character on a German
       keyboard in the SQL editor, MySQL Workbench would crash after
       advancing from the backtick using Space while the
       code-completion drop-down was visible. (Bug #18445851)

     * Visual Explain could fail to function for large EXPLAIN plans.
       (Bug #18373387, Bug #71973)

     * MySQL Workbench will now use the default schema when set, or
       use the last active schema even if after closing MySQL
       Workbench. Before, the last active schema was not preserved
       after a restart. (Bug #18352922, Bug #71900)

     * On Mac OS X, when a Model Validation Plugin was executed on a
       non-empty document, only the first of the calls succeeded. All
       subsequent calls to these plugins showed an "Cannot execute
       db.plugin.wb.validate. Plugin requires unavailable argument
       value" error. (Bug #18338544, Bug #71917)

     * Labels could be cut off from the exported image when exporting
       a Visual Explain, if there were "many" objects. (Bug
       #18374308, Bug #71980)

     * The bundled MySQL client library was upgraded to version
       5.6.17, to solve the following MySQL client issue:
       MySQL client programs from a Community Edition distribution
       could not connect using SSL to a MySQL server from an
       Enterprise Edition. This was due to a difference in
       certificate handling by yaSSL and OpenSSL (used for Community
       and Enterprise, respectively). OpenSSL expected a blank
       certificate to be sent when not all of the --ssl-ca,
       --ssl-cert, and --ssl-key options were specified, and yaSSL
       did not do so. To resolve this, yaSSL has been modified to
       send a blank certificate when an option is missing. (Bug
       #18070573)

     * The File, Import, Import DBDesigner4 model operation would
       fail and generate an error. (Bug #11766079, Bug #59115)

On behalf of the MySQL Workbench and the MySQL/ORACLE RE Team.