List:Announcements« Previous MessageNext Message »
From:Hery Ramilison Date:March 4 2014 1:12pm
Subject:MySQL Workbench 6.1.2 Beta has been released
View as plain text  
Dear MySQL users,

The MySQL developer tools team announces 6.1 Beta 2 - the start of the
public beta testing phase of MySQL Workbench 6.1

MySQL Workbench 6.1 is the upcoming major update for the official MySQL
graphical development tool.
Introducing over 30 new features, this version has many significant
enhancement focusing on real-time performance assessment and analysis
from the SQL statement level to server internals and file IO. You'll
see this in additions to the SQL Editor as well as new dashboard
visualization and reporting that takes advantage of MySQL Server 5.6
and 5.7 Performance Schema, and enhancements to the MySQL Explain Plans.

Additionally Workbench 6.1 this leveraging work from various teammates in
MySQL Engineering in 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 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 making
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 peformance
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 a new High contrast color
theme in Windows.
* 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

For discussion, join the MySQL Workbench Forums:

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

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

Quick links:
- Download:
- Bugs:
- Forums:


Changes in MySQL Workbench 6.1.2 (2014-03-04)

Functionality Added or Changed

   * The ability to select multiple processes in the Client
     Connections table was added. (Bug #18043979)

   * When an error is generated while synchronizing a model to a
     database, the statement causing the error is now displayed
     alongside the generated error. (Bug #13702410, Bug #64208)

   * Create Model from SQL Script with Place imported objects on a
     diagram checked now prompts to configure the diagram
     dimensions, which is especially useful when a lot of objects
     are imported. (Bug #11764060, Bug #56848)

   * The validation routine now checks whether a column referred to
     by an FK has the same character set as the source column. (Bug
     #11749091, Bug #38136)

Bugs Fixed

   * On Mac OS X, general stability improvements were made to the
     codebase. (Bug #18132375, Bug #71473)

   * The Visual Explain feature did not function with MySQL Server
     5.7. (Bug #18141803, Bug #71464)

   * Data Export could only be opened once per session. If the
     connection was closed and reconnected, then it would work
     again (but only once). (Bug #18149809, Bug #71506)

   * Executing a DROP from within the UI (via right-click on a
     database in the schema navigator) would cause the UI to freeze
     while the DROP operation was executed. (Bug #18123337, Bug

   * A MEB backup could not be scheduled for December 31. (Bug

   * Dropping a schema that had non-committed or reverted
     transactions could crash MySQL Workbench, but now the drop
     statement is executed as a user command so it can be aborted.
     (Bug #18054944, Bug #71327)

   * After editing an SQL file from outside of MySQL Workbench that
     was also open inside MySQL Workbench, a refresh would update a
     different (wrong) SQL editor tab in MySQL Workbench. (Bug
     #18051499, Bug #71321)

   * Sorting by a column would sort the data starting with
     uppercase characters first, before sorting the lower case
     strings. The sorting algorithm now behaves like a typical
     ORDER BY clause, which does not prioritize uppercase
     characters. (Bug #17993866, Bug #71195)

   * On Mac OS X, executing Synchronize Database could crash MySQL
     Workbench. (Bug #18000412, Bug #71203)

   * On Mac OS X, Command + F did not open a search box in the SQL
     editor. (Bug #18055066, Bug #71326)

   * Having SQL_MODE set to "MYSQL40" would not allow the ALTER
     TABLE action to create new columns in MySQL Workbench. (Bug
     #18055044, Bug #64741)

   * On Mac OS X, the auto completion popup window remained open
     after reopening MySQL Workbench. (Bug #17799326, Bug #70912)

   * MySQL Workbench would freeze when the connected MySQL server
     stopped responding, when the context help was running. (Bug

   * On Microsoft Windows, increased support for "High Contrast"
     modes was added. (Bug #17694247, Bug #70750)

   * The SQL editor could lose newline characters. The new forms
     editor is useful for this type of input, as the newlines are
     preserved. (Bug #17559560, Bug #70519)

   * After creating two tables with an n:m relationship, attempting
     to create an n:m identifying relationship between the two
     tables would yield a misleading prompt that read "Select the
     Table to receive the Foreign Key." (Bug #17449878, Bug #67864)

   * The Search Table Data tool would fail to function when used to
     search multiple schemas. (Bug #17404072, Bug #70232)

   * While executing Database, Synchronize Model..., adding a
     ROW_FORMAT definition (such as "ROW_FORMAT = COMPACT;") would
     not add a valid ROW_FORMAT definition on the next execution of
     Synchronize Model..., and instead an invalid (empty)
     "ROW_FORMAT =" was added. (Bug #17454626, Bug #70129)

   * The diagram page size is now properly passed on to printer
     driver. For example, defining a diagram with an A3 page size
     now sends A3 to the printer driver, when before it reverted to
     A4. (Bug #17389155, Bug #70191)

   * On Microsoft Windows, the Indexes section would disappear
     after restoring (after an undo) a table change from the
     history tab. (Bug #17299519)

   * When executing Database, Synchronize with any source on a
     model, the model schema was unintentionally renamed when
     enabling the Override Target option. (Bug #17299799)

   * On Microsoft Windows, Control + V would not paste a copied
     diagram. (Bug #17299778)

   * Using Create EER Model from Script would sometimes close the
     model without defining a schema. (Bug #17299745)

   * Tables created with the n:m identifying relationship tool were
     missing the created timestamp. (Bug #17050577, Bug #69656)

   * On Linux, when closing a script tab that carried unsaved
     changes in the SQL editor, the model dialog that prompted to
     "save the script first" could become hidden behind the main
     MySQL Workbench window. (Bug #16672658, Bug #68802)

   * The Scripting file chooser would generate an exception
     (without an option to cancel) when an unsupported file type
     was selected. A new Cancel button was added to this dialog.
     (Bug #14520515, Bug #66453)

   * Selecting an element in a section (when the section was longer
     than the visible part of the overview panel) would scroll the
     view back up to the top of the panel, instead of preserving
     the current cursor focus. (Bug #14520978, Bug #66420)

   * The birds-eye image of the object canvas in the navigator view
     of the model sidebar did not always show the correct z-order,
     when objects overlapped on the canvas. (Bug #14456188)

   * Using a MySQL script that started with an empty line to create
     an EER diagram would generate an empty EER diagram. (Bug
     #14278179, Bug #65749)

   * When setting "On Delete" and "On Update" to "SET NULL" on
     Foreign Key fields that were marked as "NOT NULL", a generic
     "ERROR: Error 1005: Can't create table" error was emitted. The
     generated error is now more specific. (Bug #13029457, Bug

   * While creating a column with the serial data type generates a
     NOT NULL constraint with a UNIQUE INDEX for the column, MySQL
     Workbench would complain about a missing Primary Key. (Bug
     #11762455, Bug #55051)

   * When executing Database, Synchronize Model, the Model and
     Database Differences step now expands the folder of each
     database that contains differences. (Bug #11758101, Bug

   * Relationship lines now snap to the closest snap point, rather
     than the most recently passed-over snap point. (Bug #11755408,
     Bug #47178)

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

MySQL Workbench 6.1.2 Beta has been releasedHery Ramilison4 Mar