MySQL Workbench Changelog

What's new in MySQL Workbench 8.0.30

Jul 26, 2022
  • Functionality Added or Changed:
  • The linked OpenSSL library for MySQL Workbench has been updated to version 1.1.1o/3.0.3. Issues fixed in the new OpenSSL version are described at https://www.openssl.org/news/cl111.txt and https://www.openssl.org/news/vulnerabilities.html. (Bug #34330186)
  • Libxml2 was updated to version 2.9.13 with this release. (Bug #34053743)

New in MySQL Workbench 8.0.29 (Apr 26, 2022)

  • Functionality Added or Changed:
  • The linked OpenSSL library for MySQL Workbench has been updated to version 1.1.1n. Issues fixed in the new OpenSSL version are described at https://www.openssl.org/news/cl111.txt and https://www.openssl.org/news/vulnerabilities.html. (Bug #33987621)

New in MySQL Workbench 8.0.28 (Jan 18, 2022)

  • Functionality Added or Changed:
  • All editions of MySQL Workbench and the bundled libraries were upgraded to use libssh 0.9.6. (Bug #33418517)
  • MySQL Workbench now supports the following platform versions: macOS 12, Windows 11, and Windows Server 2022.
  • Bugs Fixed:
  • Before MySQL Workbench 8.0.27, a connection using SSL attempted to establish an encrypted connection by default if the server supported encrypted connections or to fall back to an unencrypted connection if an encrypted connection could not be established. The default behavior was changed in version 8.0.27 to always require SSL encryption, which could cause a connection test to fail if the server did not support encryption. In addition, the settable values for the Use SSL field no longer included No or If available.
  • This fix restores the previous default behavior (If available) and also restores the full set of Use SSL values for establishing encrypted and unencrypted connections. (Bug #105327, Bug #33507869, Bug #105462, Bug #33541199)

New in MySQL Workbench 8.0.27 (Oct 19, 2021)

  • The linked OpenSSL library for MySQL Workbench has been updated to version 1.1.1L. Issues fixed in the new OpenSSL version are described at https://www.openssl.org/news/cl111.txt and https://www.openssl.org/news/vulnerabilities.html. (Bug #33309907)
  • Libxml2 was updated to version 2.9.11 with this release. (Bug #32993810)
  • All editions of MySQL Workbench and the bundled libraries were updated to use SQLite 3.36.0. (Bug #32765056)
  • MySQL Workbench now supports the following new connection methods for use with LDAP pluggable authentication and Kerberos pluggable authentication:
  • The LDAP User/Password connection method for simple LDAP authorization on Linux and Windows hosts.
  • The LDAP Sasl/Kerberos connection method, which uses GSSAPI/Kerberos to authenticate users and passwords on Linux hosts.
  • The Native Kerberos connection method, using authentication tokens generated by the kinit command, on Linux and Windows hosts.
  • The new authentication-based connection methods are not supported on macOS hosts. For requirement and setup information, see LDAP and Native Kerberos Connection Methods.

New in MySQL Workbench 8.0.24 (Apr 20, 2021)

  • Functionality Added or Changed:
  • The linked OpenSSL library for MySQL Workbench has been updated to version 1.1.1J. Issues fixed in the new OpenSSL version are described at https://www.openssl.org/news/cl111.txt and https://www.openssl.org/news/vulnerabilities.html. (Bug #31957287, Bug #32260611)
  • The following third-party libraries were upgraded in this release:
  • AT-SPI
  • Cairo
  • FreeTDS
  • GDAL/OGR
  • HtmlRenderer (System.Drawing.Html)
  • iODBC
  • libgcrypt
  • Libintl
  • libgpg-error
  • Libpng
  • libssh v0.7.5-openssl1.1_patch
  • Libzip
  • PCRE (Perl Compatible Regular Expressions) Library
  • Pixman
  • PROJ.4
  • PyODBC
  • PySQLite (removed)
  • TreeViewAdv for .NET
  • VSQLite++
  • Bugs Fixed:
  • MySQL Workbench 8.0.23 closed unexpectedly after starting on macOS systems. This fix adds the Python 3.7 framework as a prerequisite for the installation. (Bug #32395192, Bug #102286)
  • Unexpected output was written to the console when MySQL Workbench was started from the command line on Linux. Adjusting the log level did not stop the output. This issue was unrelated to log suppression and was eliminated by resolving a different issue. (Bug #32106379)

New in MySQL Workbench 8.0.23 (Jan 19, 2021)

  • Functionality Added or Changed:
  • MySQL Workbench now uses Python 3 for functionality such as migration, scripting shell, administrative tasks, and its SQL IDE. MySQL Workbench also ensures that installations on macOS (10.15 and later) have a valid version of Python available rather than relying on an operating system to provide the necessary scripting language.
  • Bugs Fixed:
  • Known issue: A change in the %cmake macro caused an error to occur when MySQL Workbench was built from source code on Fedora 33 using the RPM package. Use the new %cmake_build macro to avoid the error. (Bug #32019872)

New in MySQL Workbench 8.0.22 (Jan 19, 2021)

  • Functionality Added or Changed:
  • All editions of MySQL Workbench and the bundled libraries were upgraded to use libssh 0.8.9. (Bug #31358556)
  • All editions of MySQL Workbench and the bundled libraries were upgraded to use OpenSSL 1.1.1g. (Bug #31296699)
  • For clarity, visual explain diagrams now include the phrase hash join within the diamond symbol in place of block nested loop when the server version is 8.0.20 or higher. (Bug #30752203)
  • Bugs Fixed:
  • The uninstall operation within the .msi file returned an invalid error message indicating that a prerequisite, which was not identified as missing during the installation, was required before MySQL Workbench could be removed. (Bug #31533466)

New in MySQL Workbench 8.0.21 (Jul 15, 2020)

  • Functionality Added or Changed:
  • A new check box was added to the dialog for resetting an expired password. When selected it indicates that the server version in use precedes MySQL 5.7. (Bug #30799058)
  • MySQL Workbench now supports the following MySQL 8.0.19 and 8.0.20 server language features:
  • DROP CHECK, ALTER CONSTRAINT, and DROP CONSTRAINT in ALTER TABLE statements.
  • Locking clause for query expressions.
  • Table values constructor.
  • Short table select syntax.
  • New requirements for the CHANGE MASTER replication statement (row format, primary key check).
  • Failed login attempts and password lock time in ALTER USER statements.
  • Format support for EXPLAIN ANALYZE statements.
  • New and changed keywords:
  • ARRAY
  • FAILED_LOGIN_ATTEMPTS
  • MASTER_COMPRESSION_ALGORITHM
  • MASTER_TLS_CIPHERSUITES
  • MASTER_ZSTD_COMPRESSION_LEVEL
  • MEMBER
  • OFF
  • PASSWORD_LOCK_TIME
  • PRIVILEGE_CHECKS_USER
  • RANDOM
  • REQUIRE_ROW_FORMAT
  • REQUIRE_TABLE_PRIMARY_KEY_CHECK
  • STREAM
  • TIMESTAMP
  • TIME
  • Bugs Fixed:
  • MySQL Workbench Migration Wizard encountered type -154 (SQL_SS_TIME2) while copying Microsoft SQL Server tables, and it returned an error on the unhandled type. This fix adds the following new SQL data types to the wizard: SQL_SS_TIME2 (supported by MySQL) and SQL_SS_TIMESTAMPOFFSET (not supported). (Bug #30884140)
  • The TableRead, TableInsert, TableUpdate, and TableDelete events for each table touched by a query did not include complete information in the Audit Inspector. (Bug #30807539)
  • Valid TABLE and VALUES statements were identified as having syntax errors in the SQL editor. (Bug #30775372, Bug #98266, Bug #30775008, Bug #98263)
  • MySQL accounts created during the prerequisite setup using the Create MEB Account button were not granted sufficient privilege to schedule an online backup or to execute a full backup on Windows. (Bug #30774786)
  • The Table Data Import Wizard returned an error when used to import a large JSON file, rather than loading the file. (Bug #30733445)
  • Text selected in the SQL editor was blocked by the highlight color. (Bug #30369329, Bug #97070)
  • A change made to the CREATE statement to rename an existing stored procedure did not revise the corresponding name in the generated DROP PROCEDURE statement when the change was applied using the editor. This fix modifies the generated statement to no longer drop the original stored procedure after it is renamed. (Bug #30103689, Bug #96289)
  • On Windows, statements that do not generate a result set, such as INSERT or UPDATE statements, caused MySQL Workbench to close unexpectedly after the EXPLAIN operation was executed and then the Result Grid output type was selected. (Bug #27576669, Bug #89745)
  • Although the installation and file path were valid, MySQL Workbench did not find the ogr2ogr and ogrinfo files when loading spatial data. (Bug #26447395, Bug #87074)
  • A column created with NULL ON UPDATE CURRENT_TIMESTAMP(6) prevented the MySQL Table Editor from showing table information, such as indexes, views, foreign keys, and so on. (Bug #26388250, Bug #86906)
  • Memory use on a Windows host was excessive when a large result set was exported to a file, causing MySQL Workbench to become unresponsive. (Bug #26139027, Bug #86430)
  • Synchronizing a database that included a table with JSON fields to the data model produced new, separate tables for the JSON data, instead of updating the original table. In this instance, the target MySQL version set in the modeling preference, 5.6.30 by default, does not support the operation. This fix sets the default version to MySQL 8.0, but the value can be adjusted by selecting Preferences, Modeling, and then MySQL from the Edit menu. (Bug #25788105, Bug #85648)
  • The zoom-out button did not alter the zoom level of spatial data when viewed from a Linux host, unless the zoom level was reset to the outermost level first. (Bug #25723313, Bug #85444)
  • MySQL Workbench became unresponsive for several minutes after a server startup attempt was made on macOS hosts. (Bug #25077227, Bug #83769)
  • No errors or warnings were reported when scheduling a backup with MySQL Enterprise Backup, although the backup did not execute as scheduled. (Bug #23562328, Bug #81788)
  • A Sybase database migration with the ODBC (FreeTDS) connection method produced an exception when the connection was tested. (Bug #23345282, Bug #81546)
  • MySQL Workbench server administration could not acquire management access to Oracle Solaris. For a list of supported platforms, visit https://www.mysql.com/support/supportedplatforms/workbench.html. (Bug #22453133, Bug #72204)
  • On Linux, edits made to values in the result grid were lost when using the pointer device to move within the grid, rather than pressing the Enter or Tab key to change the focus. (Bug #20742151, Bug #76387)
  • Forward engineering a valid MySQL Workbench model was unsuccessful when the operation was performed using a MySQL 5.5 server instance. (Bug #20637664)
  • On macOS, a query containing SELECT @@hostname returned the column header, but the query did not show any visible output unless the first row below the column header was selected. (Bug #20540937)
  • After reverting changes made to triggers in a schema that had been saved and synchronized, MySQL Workbench was not able to locate any differences when the reverted schema was re-synchronized with the model. (Bug #20222031)
  • A connection saved with MySQL Workbench Migration Wizard was no longer visible in the wizard after MySQL Workbench was upgraded to a later version. An attempt to save the connection again, using the same name, returned an error indicating that the original connection was preserved. (Bug #18454574)
  • No connection could be made to the PostgreSQL database system when it was selected as the source in MySQL Workbench Migration Wizard on macOS. (Bug #17299989)

New in MySQL Workbench 8.0.20 (Apr 27, 2020)

  • Version 8.0.20 has no release notes.

New in MySQL Workbench 8.0.19 (Jan 13, 2020)

  • Functionality Added or Changed:
  • Important Note:
  • MySQL Workbench 8.0.19 is unable to open a new connection to MySQL Server from the home screen if the server is not started and you cannot start a server by using the Workbench Administration feature. Administrative and SQL editing tasks require an online server for the duration of this issue. Feature tasks that you performed with an offline server in previous releases now return an error message indicating that the server is unreachable.
  • This issue is limited to MySQL Workbench 8.0.19. Thank you for your patience.
  • Workaround: Start MySQL Server independently before opening the Administration and SQL Query tabs in MySQL Workbench. On Linux, you can replace the MySQL Connector/C++ 8.0.19 library with the 8.0.18 library.
  • A new context menu item now copies the headers and rows of queried data with tabs as separators, making it convenient to copy and paste query results into Excel. Thanks to Raj Rao for the patch. (Bug #30568824, Bug #97712)
  • The following MySQL server language features are now supported: value references in INSERT statements, new options (TLS version, cipher suite, compression, and privilege check) in CHANGE MASTER TO replication statements, random passwords in CREATE USER and ALTER USER statements, EXPLAIN ANALYZE, and binary collation names.
  • Context help for the keywords and functions in SQL queries now includes updated syntax and usage information.
  • Bugs Fixed:
  • When attempting to export MySQL 5.7 data using MySQL Workbench 8.0, the server returned an error indicating that INFORMATION_SCHEMA.COLUMN_STATISTICS was an unknown table. Consistent parameter use with mysqldump now skips the table as expected. (Bug #30515899, Bug #97520)
  • The SQL editor applied syntax-error highlighting to the EXPLAIN keyword in a valid statement prefixed with EXPLAIN ANALYZE, but the statement executed as expected. (Bug #30478023, Bug #97416)
  • A syntax error was generated for valid ANALYZE TABLE statements with either the UPDATE HISTOGRAM or DROP HISTOGRAM clause. (Bug #30449796, Bug #97281)
  • Storage engines not supported by MySQL were listed as possible engines that could be selected for tables. Unsupported storage engines now are removed from the suggestion list. (Bug #30338754, Bug #96968)
  • An existing stored connection could not be replaced with a new connection having the same name when the attempt was made from the Source Selection step of the MySQL Workbench Migration Wizard. (Bug #30269513)
  • On macOS, the Cancel and Export buttons in the Export Recordset context window (for SQL INSERT statements) were mostly hidden. (Bug #30244028, Bug #96689)
  • If the ls command produced an error message together with a list of files, no audit log for the error appeared in the Enterprise MySQL Audit Log Inspector. (Bug #30135391)
  • An original SQL Server record (for example, 1020.6) was copied inaccurately to the corresponding MySQL column (1020.0) when migrated using the DECIMAL data type. Similarly, data migrated using the NUMERIC type generated a type-conversion error. Now, both decimal and numeric values are stored as DECIMAL types to fix the resolution of the decimal value or to fix the type conversion. (Bug #30062094, Bug #96230, Bug #30263415, Bug #96744)
  • The uniqueidentifier data type in a SQL Server source table was interpreted during migration as type VARCHAR(64) UNIQUE in the MySQL target column, instead of a VARCHAR column to represent a GUID (UUID) that is not unique. (Bug #29355468, Bug #94066)
  • The relationship arrows within an EER diagram were not visible when the Dark Mode theme was enabled on a macOS host and the diagram was exported as a single page PDF file. This fix disables the theme in models to prevent conflicts with the colors assigned by the model editor. (Bug #29307893, Bug #94174)
  • An empty file list was shown when the audit_log_file value was set to any location other than the MySQL server data directory. (Bug #22673089)

New in MySQL Workbench 8.0.18 (Oct 14, 2019)

  • 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. (Bug #30105715, Bug #96357)
  • The visual SQL editor reported a false error on the RENAME COLUMN clause of a valid statement. (Bug #29938388, Bug #95901)
  • 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. (Bug #29931969)
  • 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. (Bug #29898662, Bug #95742)
  • 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. (Bug #29771365, Bug #29894485)
  • 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. (Bug #29746607)
  • 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. (Bug #29692955, Bug #95131)
  • The Ubuntu 19.04 distribution did not include MySQL Workbench support as expected. (Bug #29690500, Bug #95118)
  • The reset operation for MySQL Enterprise Firewall rules produced an exception, instead of resetting the rules. (Bug #29681550)
  • The informational message shown when removing MySQL Enterprise Firewall was corrected. (Bug #29681305)
  • A blank MySQL Enterprise Firewall rule could be submitted, which generated an exception. (Bug #29680813)
  • MySQL Enterprise Firewall could not be enabled from MySQL Workbench after it was uninstalled and then reinstalled. (Bug #29547778)
  • Error messages within the Administration - Online Backup tab used incorrect characters to represent versions of MySQL Server. (Bug #29455453)
  • 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. (Bug #29394563, Bug #94430)
  • 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. (Bug #29290375, Bug #94151)
  • Unexpected cursor movement occurred within the query editor when using up and down arrow keys on computers running macOS 10.14 (Mojave). (Bug #29049404, Bug #93576)
  • 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. (Bug #29049379, Bug #29049224)
  • 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. (Bug #29024631, Bug #29127415)
  • Connections made to 5.6 and 5.7 server instances used the utf8 character set, instead of utf8mb4. (Bug #28912563, Bug #93136)
  • The opening and closing brackets were missing from the Type column output within the Administration - Server Logs tab. (Bug #28686449)
  • On computers running Windows, scrolling up and down with a pointer device was impaired. (Bug #28686322)
  • Test Connection functionality remained enabled for stored connections after they were deleted. (Bug #28672121)
  • 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. (Bug #27785104, Bug #89866)
  • The PYC file associated with a plugin remained in the modules directory after the plugin was uninstalled. (Bug #24522488)
  • The MySQL Enterprise Firewall plugin was not recognized by MySQL Workbench when MySQL was installed from source. (Bug #23617930)

New in MySQL Workbench 8.0.17 (Jul 22, 2019)

  • Functionality Added or Changed:
  • All editions of MySQL Workbench and the bundled libraries were upgraded to use OpenSSL 1.0.2r. (Bug #29489010)
  • MySQL Workbench grammar updates now enable the language features of each supported MySQL server version from MySQL 5.6 to MySQL 8.0, including the new language features in MySQL Server 8.0.17 (see MySQL).
  • The implementation for SSH connections now uses libssh version 0.8.7, which replaces the previous version of libssh.
  • Bugs Fixed:
  • An empty page was shown when Show License Info was selected from the Help menu. (Bug #29821258)
  • Remote management did not work after the SSH port number on the destination computer was changed; instead, it continued to use the default port number. (Bug #29784254, Bug #95221)
  • On Windows, an error at startup prevented the successful fetching of database objects for display in the Schemas tab. (Bug #29772769, Bug #95335)
  • The informational dialog box did not open after About Workbench was selected from the Help menu on hosts running Ubuntu 18.04.2 LTS. (Bug #29754218)
  • Database objects were not fetched as expected when any schema shown in the Schemas tab (located in the Navigator sidebar panel) for a valid connection was expanded. (Bug #29752794)
  • The Reverse Engineering Database wizard stopped working during the final step and generated an error message on hosts running Fedora 29. Also, general editing activities were affected. (Bug #29598807, Bug #94894, Bug #29528028, Bug #94757)
  • A syntax error in a view that was generated using the view tool within an EER model caused MySQL Workbench to stop working when the view was closed. (Bug #29558534)
  • An attempt to create an EER model by reverse engineering a script and selecting a dump file generated errors instead of creating the model. (Bug #29535589)
  • The copy_migrated_tables.cmd batch file, generated by the Migration Wizard, closed without performing the expected tasks after file was executed properly. (Bug #29516531)
  • The online backup operation returned an error indicating insufficient privileges for an account with sufficient privileges. (Bug #29515528)
  • An exception was raised when a new firewall rule was added without also selecting the option to indicate that the rule (or SQL statement) is a normalized rule. (Bug #29514458)
  • An exception resulted when any variable category was right-clicked within the Administration – Status and System Variables tab. (Bug #29509495)
  • An exception resulted when Show Columns was selected (right-clicked) to enable a column for any of the cache entries shown in the Administration - Audit Inspector tab. (Bug #29508773)
  • Backup files (.ibd) generated with the compression option enabled were not compressed (.ibz) after the operation finished. (Bug #29253624)
  • On Windows, SSH connections in combination with MySQL Enterprise Backup operations are available for use only when the server is local. (Bug #29215730)
  • The text for advanced options (Data Export from the Server menu) was modified to remove errors. (Bug #29024143, Bug #93508)
  • An incorrect password did not disable the Next button during the forward-engineering of a valid model, but then the next step generated an access-denied error while permitting the next action to continue after the error. Now, a valid password is required before the next step in the operation is available to select. (Bug #25951080, Bug #86064)
  • Regardless of the source objects selected (and displayed) during the migration operation, all objects were migrated if the steps of the wizard were repeated with the Next and Back buttons. (Bug #25121122, Bug #83876)

New in MySQL Workbench 8.0.16 (May 24, 2019)

  • Functionality Added or Changed:
  • The script editor now highlights matching pairs of parentheses when one of the pair is selected. (Bug #27473434, Bug #73167)
  • Microsoft Visual Studio support was upgraded from Visual Studio 15 to Visual Studio 17.
  • Previously, the output from running schema validation plugins on a MySQL model was distributed to different areas of MySQL Workbench, making portions of the information easy to miss. The same functionality now is shown in a single location and reorganized to provide informational, warning, and error messages by category. A new Validate tab also provides a simple way to reselect and rerun validation tests from the output area in the right side panel (see Schema Validation Plugins).
  • Bugs Fixed:
  • MySQL Workbench stopped working when an existing table with an expression in a column of type BINARY was selected for editing. (Bug #29449200)
  • MySQL Enterprise Firewall could not be installed from the Enterprise Edition of MySQL Workbench. (Bug #29359957, Bug #94335)
  • An incorrect-integer-value error resulted when the Table Data Import Wizard attempted to import CSV data to a valid database table. (Bug #29348922)
  • MySQL 5.7 tables exported to MySQL 8.0.14 or 8.0.15 produced the following error: Unknown table 'COLUMN_STATISTICS' in information_schema. (Bug #29344344, Bug #94294)
  • A successful connection made with SSH tunneling from a Linux host produced an ongoing loop of errors if an attempt was made to close the connection. (Bug #29342871, Bug #94212)
  • The LATERAL keyword now conforms with the SQL editor convention to highlight and indent the words considered keywords by MySQL. (Bug #29251184, Bug #94012)
  • An exception was raised when a valid path to the MySQL Enterprise Backup 8.0.14 or 8.0.15 executable was provided in the prerequisite settings. To back up MySQL 8.0.14 or 8.0.15 data, upgrade to MySQL Workbench 8.0.16 or use MySQL Enterprise Backup 8.0.14 or 8.0.15 directly (see Introduction to MySQL Enterprise Backup). (Bug #29246551)
  • An error in the generated mysql_rdbms_info.xml file caused MySQL Workbench to stop working. (Bug #29237703, Bug #93987)
  • The size of the Table Data Import Wizard window changed unexpectedly between steps, causing the navigation buttons to vanish from visible range unless the window was expanded to include them. (Bug #29200662, Bug #93869)
  • With the GNOME desktop theme set to Adwaita (default) or Adwaita-dark, text selected within the SQL editor was invisible. (Bug #29184506, Bug #93847)
  • The Command-V keyboard shortcut on macOS returned an error indicating that a paste-row operation was attempted, rather than the single-value paste used to edit a field within the result grid following a successful query. (Bug #29137004, Bug #93710)
  • Executing a function or stored procedure caused an unexpected program shutdown on Linux hosts. (Bug #29134435)
  • The SQL beautifier feature produced no change when it was executed within the Triggers tab of the table editor. (Bug #29133592)
  • The table inspector did not start properly and produced an error on macOS when it was selected from the context menu of a valid table within the Schema tab. (Bug #29128333)
  • An exception was generated when the results of a query was toggled between visual explain and tubular explain formats within the Execution Plan tab. (Bug #29121364)
  • A user account that was deleted properly from Users and Privileges remained visible until the Administration tab closed and reopened. (Bug #29061678)
  • New tables added to the canvas of an EER diagram displayed the table name bar only, without columns, when the table tool (Place a New Table) from the vertical toolbar was used to add each table. (Bug #29056873)
  • Records imported from an external file, such as a CSV file, generated an exception when the operation was attempted from a macOS host. (Bug #29048933)
  • Each step shown in the MySQL Workbench Migration Wizard was masked and unreadable while the individual operation executed. This fix modifies the contrast between the text of the current step and the box used to highlight it. (Bug #29048871)
  • On Windows 10, the scroll wheel (or mouse wheel) did not respond when used to scroll in any on-screen area with a scroll bar. (Bug #29035906, Bug #93541)
  • Some keyboard shortcuts, such as Command-C, did not work within the SQL and model editors on macOS 10.14 hosts. (Bug #29034285, Bug #93186)
  • Rather than generating a warning or error when it detected an unknown SSH option in the ~/.ssh/config file, MySQL Workbench became unresponsive. (Bug #29016708, Bug #92972)
  • The column-statistics option (Advanced Options) was selected by default in the Administration – Data Export tab, which prevented the successful export of databases from the 5.6 and 5.7 servers. (Bug #28918423, Bug #92928)
  • The SQL editor and the Alter Table operation both reported errors on indexes with valid functional key parts and on expressions that were used as default values. (Bug #28832740, Bug #92908, Bug #28831069, Bug #92900)
  • The actions selected from the history-palette context menu did not produce any results. (Bug #28721233)
  • The code auto-completion feature in the query editor did not provide the expected behavior. (Bug #28443700, Bug #91859)
  • The Close Other Tabs action closed all tabs in the SQL editor when it was selected from the context menu of the New table - table tab. (Bug #28257404)
  • MySQL Workbench stopped working on Linux hosts after a long period of use that included adding new tables to an existing model. (Bug #28257141)
  • With a set of objects selected to import from the dump project folder, only the first object of the set was shown in the Schema Objects list, instead of all selected objects. In addition, the first object was repeated multiple times in the list. (Bug #28222744)
  • MySQL Workbench was unable to start a session to the server on MacOS hosts until a successful login was performed at the command line first. (Bug #28165625)
  • Some keyboard shortcuts were unsuccessful when used properly. (Bug #28108104, Bug #91090)
  • A valid query using an appropriate server version for window functions displayed a syntax error at the opening parenthesis of the first OVER clause in the query editor. (Bug #27922827, Bug #90620)
  • The template that was generated for a table of a model did not include type values within the Datatype column. (Bug #27025456)
  • Items listed within the Schemas tab were not visible when selected on Linux. (Bug #26579157, Bug #87321)
  • The test-connection action in older versions caused MySQL Workbench to stop working when it was used to test standard TCP/IP over SSH connections during the initial setup. (Bug #21144432)
  • A warning was generated during attempts to migrate source tables from Microsoft SQL Server with a valid ODBC driver if a column name included unrecognized characters. The reverse engineering operation reported that an impacted table had no column attributes, and the migration stopped with errors later in the process. (Bug #18109616, Bug #71336)
  • The operation to check for MySQL Workbench updates (from Help) returned an error when used behind a proxy server with authentication. (Bug #13864621, Bug #64308)

New in MySQL Workbench 8.0.15 (Feb 5, 2019)

  • This release contains no functional changes and is published to align version number with the MySQL Server 8.0.15 release.

New in MySQL Workbench 8.0.14 (Feb 5, 2019)

  • Functionality Added or Changed:
  • MySQL Workbench now supports macOS 10.14 Mojave, including full compatibility with the Dark Mode color scheme. (Bug #28831956, Bug #92902)
  • The Adv. Find tab operation that searched an open EER diagram by database objects only was removed. (Bug #28740047)
  • All editions of MySQL Workbench and the bundled libraries were upgraded to use OpenSSL 1.0.2q. (Bug #28695759)
  • Keyboard access was added to the home screen tab to enable navigation using the Tab and Enter keys. In addition, the screen view now scrolls to display a selected item if the item was off-screen when highlighted with the Tab key.
  • On Windows and Linux hosts, the Application key and Ctrl+F10 now open a menu of commands (context menu) related to the selection.
  • The following new functions were added to the Workbench GRT module:
  • activateDiagram()
  • Opens the selected EER diagram for use with the exportPNG, exportSVG, exportPS, and exportPDF functions.
  • exportDiagramToPng(, )
  • Performs a PNG export of an EER diagram to the path provided without activating it.
  • Two redundant features were removed from all platforms:
  • The connection information pop-up sheet on the home screen tab
  • Instead, open Manage Connections from the Database menu (or Edit Connection from the context menu of each connection) to view connection details.
  • The merge icon (two arrows pointing at each other) located in the Navigation area of the side panel
  • Content from the Administration and Schemas tabs were merged or split when this icon was toggled. Now, the administration section links and schema tree appear in separate tabs only.
  • Bugs Fixed:
  • Valid decimal data within a Microsoft SQL Server table generated an error when used with the MySQL Workbench Migration Wizard. (Bug #28962023, Bug #93293)
  • The InnoDB status shown within the Administration – Dashboard tab displayed the wrong usage percent. (Bug #28919419)
  • A conflicting dependency was removed that prevented the mysql-connector-c++-devel package installation when MySQL Workbench was installed first. (Bug #28915929, Bug #93172)
  • The on-screen process of editing a stored procedure did not prompt to save the changes. (Bug #28880743, Bug #93068)
  • A new table added to an existing model caused MySQL Workbench to stop working. (Bug #28879925, Bug #93067)
  • The alter-table operation when applied to partitioned tables on Windows caused MySQL Workbench to stop working. (Bug #28856542, Bug #92990)
  • Characters from Cyrillic character sets when included in the path to SSH key files caused valid connection attempts to fail without producing a clear error message. These characters now are permitted within the path. (Bug #28814329, Bug #92847)
  • Connections made to a remote MySQL server over SSH did not recover properly after the network was interrupted temporarily. (Bug #28806660, Bug #90884)
  • New accounts created to use standard authentication were instead created to require strong password encryption when the default_authentication_plugin server system variable was configured with the caching_sha2_password value. (Bug #28777856, Bug #92740)
  • The default user name, newuser, was not accepted when it was used to create a new account. (Bug #28776902, Bug #92738)
  • The operation to migrate a Microsoft SQL Server schema produced an error when it encountered problematic tables during the reverse-engineering step. (Bug #28747888, Bug #92659)
  • A table editor tab that was opened by clicking the table icon from within the sidebar (Schemas tab) displayed the correct SELECT * FROM query and results, but the query text did not line up along the left margin as expected. (Bug #28730407)
  • Context-menu actions (New Tab, Save Tab, or Copy Path to Clipboard) when applied to an open SQL editor tab caused the tab to close unexpectedly on Linux. (Bug #28721377)
  • The color used to highlight a query in the SQL editor was the same color used for the text, which made the selected query appear to be missing when it was highlighted. (Bug #28691256, Bug #92535, Bug #28715080)
  • The Report a Bug action from the Help menu returned an error instead of opening the MySQL bug database on macOS systems. (Bug #28612380, Bug #92327)
  • The last file selected from a previous directory during any browse operation was carried over after navigating to a new directory and without selecting a new file from the directory. Files now must be selected explicitly within the browse dialog box. (Bug #28608962, Bug #92104)
  • Some columns within a Microsoft SQL Server database table were not migrated as expected. The operation returned an error when copying mixed data types. (Bug #27838190, Bug #84777)
  • Multiple SQL queries executed sequentially in separate tabs did not resolve as expected on Windows. The first query ran to completion, but the tab would not close. The second query never finished. Thereafter, no additional queries could run and the program would not exit. (Bug #25965655, Bug #86090)
  • The Migration Wizard was unable to retrieve a schema list from source when the source RDBMS was Microsoft SQL Server and a valid FreeTDS driver (required by Linux) was provided. (Bug #25457611)
  • No context help was displayed with a view or stored procedure in the SQL editor. (Bug #24697574)

New in MySQL Workbench 8.0.13 (Feb 5, 2019)

  • Server Support:
  • Support for MySQL 5.5 by MySQL Workbench 8.0 was removed. If you still need to use MySQL Workbench on a MySQL 5.5 server, you can use MySQL Workbench 6.3, which is available from MySQL Product Archives (see https://downloads.mysql.com/archives/workbench/).
  • Functionality Added or Changed:
  • MySQL Workbench on macOS 10.14 Mojave was tested with positive results. The new Dark Mode feature is not yet compatible with all screens and should not be enabled for this release.
  • Bugs Fixed:
  • With valid geometry points inserted, the option to open the points in a browser failed on macOS hosts because the URL was improperly formed. (Bug #28587193, Bug #92266)
  • An apostrophe character (') within a table comment generated a parsing error when an attempt was made to alter the table. (Bug #28552873, Bug #92191)
  • Insufficient privilege was granted during the attempt to create a new MySQL Enterprise Backup user account. Although valid prerequisite backup information was provided, the validation script returned the following error message: Access denied for backup account. (Bug #28536272, Bug #92115)
  • When remote management with SSH was enabled, attempting to insert the required passwords in the Options file produced an error message. After the error was closed, the Administration tab became unresponsive and MySQL Workbench did not shut down properly. (Bug #28519087, Bug #92061)
  • An error with the following message was generated when the export operation was executed on tables from an earlier server version: Unknown table 'COLUMN_STATISTICS' in information_schema (1109).
  • Because the version of mysqldump used with the operation can differ from that of the target server, some features may not be exported as expected when the versions are mismatched. A warning message now provides a description of the condition, along with instructions to resolve the version mismatch, or the option to continue anyway. (Bug #28471433, Bug #91640)
  • On Windows hosts, the history of scheduled MySQL Enterprise Backup jobs was not persisted in the dashboard between MySQL Workbench sessions. This fix eliminates the issue; however, the existing mysqlwbmeb.vbs file must be removed before scheduling new backup jobs. (Bug #28430457)
  • The default target version of MySQL to use with MySQL Workbench models was set to MySQL 5.6.30 and did not increment automatically. With this fix, the value now defaults to the latest version. The default target version can also be set manually (see Preferences: Modeling: MySQL). (Bug #28397515, Bug #91782)
  • Executing queries over an period of time caused the existing result grid in each query tab to be hidden when the grid was previously visible and prevented the results grid in new tabs from showing. (Bug #28361489, Bug #91265)
  • After copying a query into a second query editor, auto-completion did not display the related column names. Instead, when auto-completion was engaged, MySQL Workbench stopped working. (Bug #28312867, Bug #91559)
  • The operation to compare schemas did not appear in the menu after a valid model was opened on Linux hosts. (Bug #28249454)
  • The filter arrows that select objects for forward or reverse engineering within wizards generated an error instead of moving the objects as expected. (Bug #26435349, Bug #26922638, Bug #87980, Bug #25921645, Bug #86013, Bug #25852505, Bug #85837, Bug #25741519, Bug #85522)
  • Schema privileges in the Administration – Users and Privileges tab (Object Rights, DDL Rights, and Other Rights) were not visible with all screen resolutions. (Bug #25584920, Bug #85079)
  • The color used to highlight a selected item in the schema tree view did not provide enough contrast from the background color to distinguish it from the other items easily. The new highlight color makes it easy to see which item is selected. (Bug #25456216)

New in MySQL Workbench 8.0.12 (Jul 27, 2018)

  • Functionality Added or Changed:
  • Important Change: MySQL model files last saved before MySQL Workbench 6.3 are no longer supported unless the models can be upgraded for use with the 6.3 release series.
  • All editions of MySQL Workbench and the bundled libraries were upgraded to use OpenSSL 1.0.2o. (Bug #27829782, Bug #28326884)
  • libgnome-keyring was depreciated and replaced with libsecret in this release on Linux platforms. Some users with existing stored passwords will be prompted to enter a password after upgrading. (Bug #27635281, Bug #89898, Bug #20291538, Bug #75345)
  • SSH tunneling support was added to the MySQL Workbench Migration Wizard and also to the wbcopytables command-line utility for copying data. (Bug #27556268, Bug #89671)
  • Performing multiple data export operations while the Administration - Data Export tab stays open now preserves custom file paths, rather than switching to the default paths for re-export operations. Exported files are automatically renamed with an incremental numeric suffix to enable repeated export.
  • In addition, a new dialog box prompts for confirmation before overwriting an existing exported file when the same path and file names are reused. (Bug #27029840)
  • OGRFree() was deprecated and replaced with CPLFree(). Thanks to Christian Hesse for the patch. (Bug #26086599, Bug #86339)
  • The SWIG prerequisite listed in the INSTALL document provided with source distributions was updated to the latest version. (Bug #25811732, Bug #85717)
  • Support for the --incremental-with-redo-log-only option was added to create backups directly from the redo log. (Bug #24960233)
  • The option to skip secure authorization is no longer available in the advanced options that apply to data import and export operations. The --skip-secure-auth option was removed in the MySQL 5.7 release. (Bug #21697062, Bug #78060)
  • The character set and collation pairings available after selecting Create a new schema in the connected server (from the main toolbar) now are sorted alphabetically in lists. (Bug #21681041, Bug #78079)
  • A new SQL export option in the Forward Engineering SQL Script wizard sorts tables alphabetically in the generated script, rather than sorting tables according to foreign-key references by default. (Bug #18551598, Bug #72289)
  • MySQL Workbench now supports the Chinese character set gb18030. (Bug #18547307)
  • The SQL editor supports online renaming of indexes with the ALTER TABLE statement. For example:
  • ALTER TABLE `sakila`.`actor` RENAME INDEX `idx_actor_last_name` TO `idx_actor_last_xxxx`;
  • (Bug #18547288)
  • MySQL Workbench now uses utf8mb4 as the connection and client character set, replacing utf8mb3.
  • Bugs Fixed:
  • Some of the controls and data were not shown within the Administration-Users and Privileges tab. (Bug #28246905, Bug #91414)
  • An attempt to add a column to an existing multicolumn index (primary key) of a table caused MySQL Workbench to stop working. (Bug #28244024, Bug #91371)
  • On Windows platforms, pasting valid content into the SQL editor was followed by the operating system becoming unresponsive. (Bug #28184916, Bug #91249)
  • A query containing SELECT COUNT(*) FROM DUAL, when saved to a script file and then opened, caused MySQL Workbench to exit. (Bug #28101684, Bug #91070)
  • With code completion enabled, defining a custom variable within a subquery caused an unexpected exit. (Bug #28040983, Bug #90915)
  • With an active MySQL 8.0.11 server connection, MySQL Workbench displayed an error message when a valid attempt was made to open Performance Reports or Performance Schema Setup. (Bug #28034685, Bug #90889)
  • Attempting to open a new query tab from the home screen (File, New Query Tab from the menu) returned an error message and closed MySQL Workbench. (Bug #28032431, Bug #90885, Bug #27781092)
  • The binlog-format option was not listed as expected within the Administration – Options File tab. (Bug #28008041)
  • When Alter Stored Procedure was selected from the context menu, MySQL Workbench stopped working. (Bug #28006985, Bug #90830, Bug #23259608, Bug #81334)
  • The advanced option, $internal$show-internal-schemas, within the Administration – Data Export tab did not expose internal schemas as expected. (Bug #27938719, Bug #90665)
  • MySQL Workbench stopped working when the CHANGE MASTER TO statement was typed directly into the SQL editor, followed by options. (Bug #27910024, Bug #90568)
  • A stored procedure without a parameter direction (IN or OUT) caused MySQL Workbench to exit when it attempted to create or alter the procedure. (Bug #27908753, Bug #90555)
  • The source-database connection password used to reverse-engineer a database was not requested and the connection failed if the password was not stored in the vault. (Bug #27882813)
  • With SSH enabled, all new connections were made to the same MySQL server instance, regardless of the port number specified. (Bug #27882278)
  • The operation that synchronizes tables with the MySQL database produced an error message when an existing column was moved to a position after a newly added column. This fix ensures that ADD COLUMN always precedes CHANGE COLUMN within the script when both are used together. (Bug #27871632, Bug #90459)
  • The table editor did not apply any changes made in the order of an index to the generated ALTER TABLE statement. (Bug #27868813)
  • Snippet execution finished with an error when the scripting shell was used. (Bug #27746883)
  • An unclear error message was displayed during the table-export operation when the file path was invalid or left empty. (Bug #27746585)
  • The shell script for copying bulk data was not generated as expected. Instead, an error message was displayed. (Bug #27745372)
  • Setting a valid command-line path for remote-server access using SSH tunneling in MySQL Enterprise Backup (on Linux) caused the validation step to fail when both the SSH and sudo users were the same. (Bug #27745200)
  • MySQL Workbench model files (.mwb) did not open as expected when double-clicked from File Explorer on Windows platforms. (Bug #27739848)
  • MySQL Workbench editors displayed text from the standard exception in the action output, rather than using an error message when SQL syntax errors were discovered. (Bug #27730102)
  • Two terminals opened when Start Command Line Client was selected from the context menu on the home screen (right-click an existing MySQL connection). (Bug #27721918)
  • Text objects when double-clicked within an EER diagram caused MySQL Workbench to stop working. (Bug #27711642, Bug #90119)
  • The shell script created during the Data Transfer Setup step of the migration process from a MySQL local connection to a MySQL SSH connection produced errors that prevented the copying of data from outside MySQL Workbench. (Bug #27670242)
  • Modifying the column order within an existing index on a table caused MySQL Workbench to exit unexpectedly. (Bug #27627986, Bug #89886)
  • The Audit Inspector cache process failed when the connection was within a group. (Bug #27567546)
  • When using the 'OmitSchemata':1 parameter in a Python script to generate a schema from an .mwb file automatically, the resulting SQL script still included the schema in each table name. This fix introduces the OmitSchemas option, which replaces both the UseShortNames and OmitSchemata options, to eliminate the schema name as expected. (Bug #27557537, Bug #84390)
  • The work area within an EER diagram was hidden after double-clicking one of the table objects to open the table editor. (Bug #27436624)
  • When two schemas were compared with Synchronize Models (from the Database menu), differences were reported consistently for stored procedures and functions even though the compared items were identical. (Bug #27436115, Bug #82151)
  • An existing MySQL model file, when selected from the home screen, generated an error (Error unserializing GRT data string too long) and did not open. (Bug #27420297, Bug #89257)
  • The sidebar panel of the EER diagram editor was cut off, making the leftmost subtabs inaccessible and forcing the diagram-zoom area to shift to the right. (Bug #27330971, Bug #89072)
  • An incorrect INSERT statement was generated when a value was inserted into a BIT column. This fix now prefixes all BIT data-type values with the character b (for example: b'0'). (Bug #27320396, Bug #89068)
  • When using the Reverse Engineer Database wizard, the objects selected during the Select Objects step could not then be deselected. (Bug #27319905, Bug #89064)
  • Column-collation changes, when made using the table editor, could not be applied. Instead, a message indicating that no changes were detected was displayed. (Bug #27297634, Bug #88985)
  • The tls_version option was not listed as expected within the Administration – Options File tab. (Bug #27272808, Bug #87964)
  • Syntax errors typed into the SQL editor are highlighted and each one can provide usage information within a tooltip while the pointer device hovers over the error. On hosts running macOS, the tooltip remained visible when the pointer device was moved off the highlighted error. (Bug #27255488)
  • When only one role in a model was assigned to a user account, the role could not be removed. (Bug #27054771)
  • Right-clicking within a new or existing script file that was opened with the Workbench Scripting Shell did not display the context menu as expected. (Bug #27037750)
  • The edit dialog box did not open when an existing snippet from SQL Additions was double-clicked. (Bug #27036975)
  • The on-screen progress of a full backup operation never changed from Starting. The correct progress was indicated in the log. (Bug #27011013)
  • Creating an MySQL model from a script, with the imported objects added to a diagram, caused MySQL Workbench to exit. (Bug #27010684)
  • The version of gtkmm30 that shipped with Red Hat Enterprise Linux 7.4 was incompatible with the version that MySQL Workbench compiled against. The version mismatch caused MySQL Workbench to close unexpectedly. (Bug #26797891, Bug #26705113, Bug #87380)
  • Catalog objects for an EER diagram were not listed, although the tables were visible in the diagram. (Bug #26747931, Bug #87662)
  • The JSON tab of the Edit Data for Value dialog box displayed large column values as negative numbers when the numbers were positive. (Bug #26741970, Bug #87646)
  • Some on-screen text within Workbench Preferences (Fonts & Colors) wrapped around to new lines rather than filling the open space on the same line. (Bug #26448300, Bug #85961)
  • The filter arrows that select objects for forward or reverse engineering within wizards generated an error instead of moving the objects as expected. (Bug #26435349, Bug #26922638, Bug #87980, Bug #25921645, Bug #86013, Bug #25852505, Bug #85837)
  • The SQL editor returned an error when valid characters were used with the utf8mb4 character set. (Bug #26142347, Bug #86454)
  • An error was reported during an attempt to back up encrypted tables using MySQL Enterprise Backup. This fix introduces the Encrypt Password option in the Options subtab for a new job within the Administration – Online Backup tab. Setting an encryption password is required to perform backup and restore operations on encrypted tables. (Bug #26135245)
  • With multiple connection tabs opened, selecting Close All But This from the context menu (right-click a connection tab) closed tabs at random. (Bug #25983146, Bug #86144)
  • Attempting to alter a table in MySQL Workbench produced an error message when the table was previously altered using a command-line client with the ENCRYPTION option set to Y or N. (Bug #25929075, Bug #86021)
  • When synchronizing a model with a database, none of the buttons for the Select Changes to Apply step were visible. In addition, some frames and options were hidden. (Bug #25906359, Bug #85963, Bug #25527078, Bug #84924, Bug #25747524, Bug #85500, Bug #26128307, Bug #86426)
  • Time stamps representing the elapsed time of backup operations were miscalculated. (Bug #25820146, Bug #85764)
  • Long comments in tables were truncated with too few characters when pasted into the SQL editor after using Copy SQL to Clipboard from the context menu within an EER diagram or the MySQL Model tab. This fix extends the threshold. (Bug #25760721, Bug #85568)
  • The attribute in source code that set the program name ('MySQLWorkbench') was omitted from Unix and Linux distributions. Thanks to Daniël van Eeden for contributing to the fix. (Bug #25725077, Bug #85460)
  • Double-clicking areas within the spatial view caused MySQL Workbench to become unresponsive. (Bug #25723306, Bug #85443)
  • The height and width of object-selection lists within the Administration - Data Export tab were improperly proportioned for the content of the lists and could not be resized. A scroll bar now enables access to all listed objects. (Bug #25716077, Bug #85308)
  • A message displayed during the startup sequence indicated that some valid operating systems were unsupported. For current platform information, see https://www.mysql.com/support/supportedplatforms/workbench.html. (Bug #25602334, Bug #85087)
  • A model exported as an SQL script could not be saved to disk when using either the Forward Engineer to Database or the Synchronize With Any Source wizard. (Bug #25569529, Bug #85030)
  • The buttons associated with renaming a diagram (OK and Cancel) were partially concealed. (Bug #25557678, Bug #85011)
  • The progress bar and Abort button were partially concealed on the screen when changes were being applied to stored procedures. (Bug #25532963, Bug #84927)
  • Each connection to an incompatible or nonstandard server opened a dialog box with a valid warning, but without an option to suppress the warning for subsequent connections. Thanks to Christian Hesse for the patch. (Bug #25519446, Bug #84885)
  • A connection made with an improper file did not return an SSL error as expected when the connection was tested. (Bug #25517237)
  • An explicit collation set on a column was reverted to the default collation each time the column specification was modified with the table editor. (Bug #25504264, Bug #84815)
  • The process running MySQL Workbench did not end on exit. (Bug #25496663)
  • The MySQL Workbench Migration Wizard returned an error message after failing to get a row count from source tables, which caused the wbcopytables utility to exit. (Bug #25496622)
  • Starting MySQL Workbench from the command line was unsuccessful on hosts running the Fedora 25 operating system. (Bug #25495120)
  • Custom settings made before executing the data export operation were not persisted if the operation was executed again (by clicking Start Export a second time). Instead, the custom settings were discarded and replaced by the default settings. (Bug #25488234)
  • Overlapping text boxes covered the full name entered for the Create a New Table option within the Select Destination step of the Table Data Import Wizard. (Bug #25476103)
  • The Copy and Copy Details operations from the Server Logs context menu (right-click a row in the log) were swapped. The Copy operation copied the details and the Copy Details operation performed a simple copy. (Bug #25469694)
  • The Copy as PHP Code (Iterate SELECT Results) command (select Tools and then Utilities from the menu) was unexpectedly disabled for valid query results. (Bug #25466399)
  • On Linux platforms, right-clicking Tables within the Catalog Tree for a valid EER diagram displayed an empty context menu. This fix minimizes the size of the empty menu. (Bug #25463963)
  • Exporting a schema from the Administration – Data Export tab returned an error when the server was configured for use within an InnoDB cluster. (Bug #25444837)
  • After maximizing and then reducing MySQL Workbench, some screen options were improperly sized or no longer visible on Linux platforms. (Bug #25415064)
  • The set of default target schemas available to choose from within the Administration – Data Import/Restore tab showed each schema listed twice on Windows platforms. (Bug #25239261, Bug #84161)
  • The table editor did not display generated columns within a user-defined table and the Alter Table operation returned an error message when an attempt was made to modify any of the nonvisible columns. (Bug #25209591, Bug #84078)
  • An error message was returned when an attempt was made to inspect a partitioned table using either the information icon or the context menu. (Bug #24973171, Bug #83605)
  • A single MySQL connection tab could not be closed unless a second connection tab was opened first. (Bug #24751859, Bug #83194)
  • With a connection made to a remote MySQL server, some context-menu functionality stopped working. For example, right-clicking a valid stored procedure from the Schemas list and selecting Alter Stored Procedure or Create Stored Procedure did not open a tab in the editor as expected. (Bug #24506578, Bug #82659)
  • On occasion, using sudo with a valid password to open a log file produced an exception. (Bug #24297921)
  • A variety of error messages were returned when attempts were made to open the Output panel (or when using Help, System Info from the menu) with older versions of MySQL Workbench. System Info was removed from the menu. (Bug #23584746)
  • The print-preview operation (File, Print Preview from the menu) did not work, or return an error message, on some Linux platforms. (Bug #23467065)
  • Executing separate queries (each in its own connection tab) caused MySQL Workbench to exit. (Bug #23305283, Bug #81480)
  • The PROJ.4 library (libproj) was not found, which prevented the initialization of Spatial Viewer. (Bug #22931452, Bug #80710)
  • A model diagram could not be reduced in size by clicking to the grid or by adjusting its value with the input controls. Attempts to reduce the size made the diagram larger. (Bug #22929861, Bug #80730)
  • Read-only tables, such as those having an index but no primary key, could be selected for update. However, the invalid update operation caused MySQL Workbench to become unresponsive before the operation finished. (Bug #22735577, Bug #80378)
  • An active connection to MySQL server was closed unexpectedly with the DBMS connection read time out (in seconds) preference option set to zero, which should keep the connection open. (Bug #22618750, Bug #80188)
  • Performance Schema instrumentation was not reset from the dashboard on Windows, even though confirmation of the change was provided. (Bug #22557320, Bug #80021)
  • When using the keyboard shortcut to comment selected lines within the SQL editor and with the cursor wrapped around to the beginning of the next line, the entire unselected next line was also commented. (Bug #22282406, Bug #77143)
  • A second view was created unexpectedly when an existing view was renamed using ALTER VIEW syntax. (Bug #22170451, Bug #79176)
  • An error message (Operation failed with exitcode 7) was generated during the dump operation when an attempt was made to export data running on a remote server. (Bug #22093554, Bug #78937)
  • The MySQL Server start and stop management operations generated unhandled exceptions. (Bug #21861171)
  • Stored procedures, when added to a model and synchronized with a database, were not listed in the Navigator area of the sidebar panel. New functions were not represented in the Catalog Tree after synchronization, although each function did appear in the Navigator area and in source. (Bug #21443566, Bug #76368)
  • Tabs separating multiple schemas within the Physical Schemas area of the MySQL Model tab were not visible. (Bug #21356922, Bug #77451)
  • The on-screen description of the myisam-repair-threads system variable was incomplete. It now indicates that the (default) value of 1 disables parallel repair (see the MyISAM tab in Administration - Option File). (Bug #20667496, Bug #76200)
  • Unexpected differences were displayed after using the Forward Engineer to Database wizard and then synchronizing the model and database. (Bug #20631631)
  • The keyboard shortcut to open the Find and Replace dialog box (or Edit, Replace from the menu) did not work from within the Workbench Scripting Shell. (Bug #20630325)
  • When importing data from a CSV file, some rows of data were not shown until Apply was clicked. This fix replaces the import functionality with a wizard. All rows now display correctly in the Configure Import Settings step of the Table Data Import wizard. Note that when no column header is provided, the first row of data is used as the header. (Bug #20630193)
  • The template supplied for the Create a Table Like operation (right-click Tables within the schema tree) was not complete enough to use without custom modifications. (Bug #20578595)
  • The wb.log file did not rotate to a new file (for example, wb.log to wb.1.log) as expected on startup. In addition, all queries were written to the sql_actions_unconnected.log file, instead of to an individual log file for each connection. (Bug #20356293, Bug #75496)
  • The Zoom + icon in the spatial view toolbar produced deteriorating resolution as an image was enlarged. For better results, use the Zoom to area icon to recompute a portion of the whole shape, instead of simply magnifying the visible area with the Zoom + tool. (Bug #20279644, Bug #75318)
  • A newly created SSH connection could not be used to synchronize a model with a MySQL database. (Bug #20144296, Bug #75102)
  • Expired root passwords were not supported by MySQL Workbench and could not be changed during the first attempt to make a connection to the server where the password was expired. (Bug #19654005)
  • Keywords in stored procedures and triggers were not highlighted consistently within the SQL editor and code blocks with keywords did not expand or collapse as expected. (Bug #19000092, Bug #72677)
  • Selecting Server and then Backup Recovery from the menu generated an unhandled exception when the server was stopped. (Bug #18492268)
  • Returned rows of a column in the result grid did not reliably sort by ascending and descending order when the column label was clicked. (Bug #18454325)
  • The Delete key did not function within EER diagrams. (Bug #18445600)
  • With both a MySQL model and EER diagram open, pressing the CTRL+W keyboard shortcut twice closed the diagram, but not the model file. (Bug #18445598)
  • On Linux platforms before the home screen was redesigned, attempting to drag and drop a connection from within a group caused the group to move instead of the connection. (Bug #18445563)
  • When editing an EER diagram, the icons within the editor overlapped on Linux platforms. (Bug #18426867)
  • Schema transfer and migration operations did not support SSH connections and produced error messages when the operations were attempted. (Bug #18138798, Bug #71295)
  • The Use defaults from global settings model option (Model, Model Options from the menu in the MySQL Model tab) when selected did not override the target MySQL version (set in Model Options) with the default target version (set in Workbench Preferences). (Bug #18130160, Bug #71429)
  • Attempting to edit a corrupted MySQL model (.mwb) file resulted in an unpredicted shutdown. (Bug #17456147, Bug #70334)
  • The Save and Save As dialog boxes did not show the file type of a model or SQL script. (Bug #17300401)
  • On macOS platforms, the database-migration operation returned various error messages when an attempt was made to migrate valid data into MySQL. (Bug #17299915, Bug #17299925, Bug #17408230)
  • Selecting multiple objects (tables, views, and so on) in a model, and then deleting all of them at once, removed only the first object from the model. (Bug #14821928, Bug #67214)
  • When an output message in the Action Area panel consisted of multiple lines, only the first line was visible. This fix provides an information box that appears briefly when a pointer device hovers over the truncated message. (Bug #14802567, Bug #66988)
  • The Workbench Scripting Shell window on hosts running the GNOME Shell lacked the controls to resize or close the window. (Bug #14768677, Bug #66810)
  • The context menus associated with tables in the schema tree did not function when the schema list was filtered. (Bug #14690217, Bug #67001)
  • The combination of Ubuntu with language-pack-tr and LANG=tr_TR.UTF-8 produced an error message when columns of type INT were parsed during operations that altered existing tables. (Bug #13971992, Bug #63872)
  • Chinese characters in the file path of an existing MySQL model were misrepresented and rendered the file inaccessible. (Bug #11757843, Bug #49950)
  • EER diagrams with long names wrapped around to a second line in the Model Overview area and were not fully visible when the host was Microsoft Windows. This fix inserts a vertical scroll bar into the Model Overview to accommodate long names. (Bug #11749931, Bug #40103)

New in MySQL Workbench 8.0.11 RC (Apr 19, 2018)

  • FUNCTIONALITY ADDED OR CHANGED:
  • Visual SQL editor: The context help has been enhanced to eliminate the requirement of having a valid MySQL connection to view the help topics. In addition, the help content now can be updated with each release of MySQL Workbench and the formatting of help topics has been improved. (Bug #25918509)
  • Microsoft .NET Framework version 4.5 replaced version 4.5.2 as the minimum requirement for installing MySQL Workbench with MySQL Installer. (Bug #25837944)
  • All links to MySQL and Oracle web pages from within MySQL Workbench now use the HTTPS protocol. (Bug #25531365)
  • Geometry fields displayed in the result grid now include a context-menu item that opens the geometry point in a browser. The selected point opens in openstreetmap.org by default, but the URL is configurable. (Bug #25517676)
  • The MySQL Workbench prerequisites web page was updated to include links to the latest Microsoft downloads. (Bug #25408896, Bug #25840902, Bug #85820)
  • The SSH Connect Timeout preference now can be configured, whereas in previous versions, this preference was set statically to 10 seconds. (Bug #18663250)
  • Platform support for Microsoft Windows Server 2016 was added.
  • Administration tabs were modified to include the latest configuration options available from servers up to and including the MySQL 8.0 release series.
  • Character sets and collations are now rendered consistently across connections, models, and all editors (schema, table, and column).
  • MySQL Workbench now supports the caching_sha2_password authentication plugin introduced in MySQL 8.0 (see Caching SHA-2 Pluggable Authentication). A user account can be reset to use the other available authentication types for making a connection.
  • MySQL Workbench source code has been reformatted according to Google style.
  • MySQL Workbench now uses C++14 (replaces C++11 in 6.3.10).
  • Support for invisible indexes was added for use when the active server supports the feature and the index is neither a primary key index nor a unique column (see Invisible Indexes). A new option in the Indexes subtab of the table editor (for both the SQL and modeling editors) provides index visibility when it is selected.
  • MySQL Workbench now provides a simple way to enable or disable the persisted global system variable settings introduced in MySQL 8.0 (see SET Syntax for Variable Assignment). For variables that can be persisted, a new check box enables configuration changes at runtime that also persist across server restarts, and applies the persisted value if one exists. Persistent system variables can be reset (to not persist) individually or collectively.
  • The layout and behavior of the graphical elements within all administration tabs now are consistent across the tabs. In addition, the sidebar Management secondary tab was renamed to Administration to match the title of the workspace tabs that open when accessing the operations listed in the Management, Instance, Performance, and MySQL Enterprise sections.
  • The following infrastructure changes were made:
  • ANTLR4 as the backend parser.
  • A new code-completion engine that works with object editors (triggers, views, stored procedures, and functions) in the visual SQL editor and in models.
  • Support for new language features in MySQL 8.0, such as common-table expressions and roles.
  • Grammar updates that synchronize with the latest MySQL servers.
  • BUGS FIXED:
  • Several tooltips within the Administration - Users and Privileges tab had inaccurate text that was corrected by this fix. (Bug #27392119, Bug #89256)
  • Columns of a table that followed a column containing a fractional seconds part did not appear within the tab opened by using Alter Table. (Bug #27314770, Bug #89053)
  • MySQL Workbench generated an error when the valid encryption instruction was improperly identified, but the query executed as expected. (Bug #27239353)
  • A differences report generated during the compare schemas operation for models could not be saved to a file. (Bug #27187659)
  • The on-screen buttons that enable saving a script to a file or copying it to the clipboard were missing from the review step of the forward-engineering operation on macOS hosts. (Bug #27162920, Bug #88612)
  • A UNION query with valid syntax produced an error message. (Bug #27113889, Bug #88456)
  • Some MySQL 8.0 keywords within a query were improperly identified as syntax errors. (Bug #27036620)
  • Importing a JSON document with the Table Data Import Wizard was unsuccessful. (Bug #27036381, Bug #25983728, Bug #86148)
  • Recorded rules were not found after the Mode option in the Firewall tab was properly configured for a valid user account. (Bug #27003240)
  • The manual editing step of the MySQL Migration wizard generated an exception when an object was selected for editing. (Bug #26986326)
  • The version of gtkmm30 that shipped with Red Hat Enterprise Linux 7.4 was incompatible with the version that MySQL Workbench compiled against. The version mismatch caused MySQL Workbench to close unexpectedly. (Bug #26797891)
  • The DBDoc Model Reporting feature omitted comments from the detailed HTML report using frames when processing a model based on a database with valid table comments and the Include DDL code for Objects option selected. Generating the report also caused MySQL Workbench to exit unexpectedly. (Bug #26436291)
  • The Table Data Import wizard ignored the user's column selection and always generated tables containing the full set of columns. Deselected columns were populated with NULL values after the import operation. (Bug #26194914, Bug #86577)
  • When typing text in the search box related to an EER diagram, MySQL Workbench became unresponsive or exited unexpectedly. (Bug #26025177, Bug #86225, Bug #26678740, Bug #87522)
  • A table or stored procedure with the ENCRYPTION table-level option in the definition prevented Workbench from parsing the definition, regardless of whether or not encryption was actually enabled. (Bug #25961450, Bug #25447637)
  • The SQL editor did not highlight syntax errors in statements as expected. (Bug #25861352)
  • Workbench closed unexpectedly when the Compare and Report Differences in Catalogs wizard attempted to save the differences report to a file. (Bug #25860643)
  • With a default schema properly selected and with the Create View icon (from the menu bar in an active connection tab) selected to open a new_view – View tab, a valid statement returned errors and then dynamically appended _SYNTAX_ERROR to the view name. For example, new_view was changed to new_view_SYNTAX_ERROR. (Bug #25860621)
  • When a new procedure on a MySQL model was created, the parser incorrectly generated a syntax error. (Bug #25851441)
  • After restarting the server from MySQL Workbench and then attempting to refresh the server log from the Administration - Server Logs tab, an error message appeared indicating that a garbage packet was received. (Bug #25760560)
  • An error message appeared when MySQL Workbench was started that improperly identified the operating system as unsupported. (Bug #25736096)
  • The forward engineering wizard did not launch when the operation was selected from the MySQL Workbench menu on hosts running macOS. (Bug #25701117, Bug #85398)
  • Changes made to a view or stored procedure associated with a model were not detected after the model was synchronized without first closing or deselecting the editor. (Bug #25671681, Bug #85246)
  • Using Alter Stored Procedure from the context menu to rename a stored procedure did not remove the original stored procedure after renaming it. (Bug #25645222, Bug #85229)
  • Two program entries were created for MySQL Workbench 6.3.9 on Windows when installed or upgraded with MySQL Installer. Only one of the programs listed in the Start, All Programs menu was a valid executable file. (Bug #25584877, Bug #85083)
  • All SQL options were missing during the SQL Export Options step of the Forward Engineering SQL Script wizard when a valid model was exported. (Bug #25559175, Bug #85012, Bug #25833972, Bug #84965)
  • Object rights, DDL rights, and other rights related to schema privileges set for a user account were not visible from the Administration – Users and Privileges tab on the Windows platform. (Bug #25527029, Bug #84923)
  • Labels and icons associated with the tables, views, and routines of an EER diagram were missing from within the Catalog tab. (Bug #25519411, Bug #84892)
  • The generated UPDATE statement was incorrect when the query included a row with a unique index, had multiple columns, and one column had the NULL value. (Bug #25510537, Bug #84856)
  • Browsing for files on a remote server using a valid SSH connection returned an error and did not display the remote files. (Bug #25495895)
  • After backing up server connections to a file on a Linux host, attempting to restore those connections from the backup file generated errors and was unsuccessful. (Bug #25492082)
  • Clicking Start Server within the Administration – Startup / Shutdown tab did not start the server on macOS hosts. (Bug #25489098)
  • The layout of Firewall Rules within the Administration – Users and Privileges tab obscured some graphical elements. This fix improves the usability. (Bug #25487997)
  • Source objects could not be viewed within the setup step when using the MySQL Workbench Migration Wizard to prepare for a database migration. (Bug #25487312)
  • The spinning circular icon on the query tab that appears when a query executes and replaces the X on the tab was absent on hosts running Linux. (Bug #25482378)
  • An exception was returned when the Continue execution until next break point button was used on a script executing within the Scripting Shell. (Bug #25476250)
  • When a new snippet was saved within the Scripting Shell, the save operation did not save the snippet properly and the snippet could not be reused after MySQL Workbench was restarted. (Bug #25471491)
  • The Run Script File action could be selected from the Scripting menu without an available script to execute. This fix disables the submenu item unless there is a script to run. (Bug #25462195)
  • Migrating a table to a database generated an incomplete definition for a binary field that was NOT NULL. (Bug #25404308, Bug #84519)
  • Altering a stored procedure that contained double dollar-sign characters ($$) as part of a variable name produced an error parsing DDL message. (Bug #25377145, Bug #84466)
  • Single quotes in string columns were not escaped properly during the database migration operation. (Bug #24939843)
  • When multiple queries were executed, only the first query was displayed in the history output area or written to the sql_history log file. (Bug #24622889, Bug #82929)
  • The invalid syntax indicator that appears on each line of the SQL editor did not change after the syntax was corrected or completed. This fix ensures that the editor re-evaluates each change. (Bug #24528088, Bug #82741, Bug #24901911, Bug #83395, Bug #24901911, Bug #83395)
  • With large text enabled on the host, some option groups were not visible to select within the forward-engineering wizard. (Bug #24486726, Bug #82633)
  • For a table with existing indexes (and SQL_MODE=ANSI_QUOTES), the Indexes tab within the table editor (opened with the wrench button in the Schemas tab of the sidebar) did not show the indexes as expected. Columns, Foreign Keys, Triggers, and Partitioning tabs were also missing objects defined in the table. (Bug #24349382, Bug #80483)
  • Unless the default syntax checker was set to SQL_MODE=ANSI_QUOTES, all double-quoted string literals were highlighted as syntax errors by the SQL editor. (Bug #24329515, Bug #82293)
  • After executing a query, MySQL Workbench often quit working or exited unexpectedly without writing to the log file. This fix improves the overall stability of the SQL editor. (Bug #24291775, Bug #82187)
  • The SQL editor underlined some keywords and reserved words in statements, indicating a syntax error, but executed the statements successfully. (Bug #23346980, Bug #24345217, Bug #82331)
  • Attempting to store a password in the vault from the Manage Server Connections window on a Windows host caused MySQL Workbench to become unresponsive. (Bug #23308198, Bug #81470)
  • When executing Explain Current Statement (Ctrl+Alt+X) from the menu on an UPDATE statement, a query plan generation error was displayed and the operation failed. (Bug #23098982, Bug #81068)
  • The Reverse Engineer Database wizard excluded tables in which the WITH PARSER clause was present. (Bug #22940775, Bug #80760)
  • A column with the STORED keyword could not be generated by using the EER Diagram or MySQL Model tabs on macOS hosts. This fix updates all of the relevant tabs to include the missing STORED option for generating a column or for editing generated columns. (Bug #22645321, Bug #80211)
  • Table rows were not generated properly when a valid Microsoft SQL Server table was migrated using the MySQL Migration wizard. (Bug #22200194, Bug #77933)
  • The forward engineering operation passed the default collation when a custom collation was defined for a schema. (Bug #22148986, Bug #79115)
  • When synchronizing a MySQL model that contained a table with JSON columns, the operation attempted to create a new table instead of fetching the table from the database. (Bug #22060787)
  • Columns with custom collation were reset to the default collation when the model containing the table was exported. (Bug #22006966, Bug #78817)
  • Models synchronized with existing databases produced an error message if any of the tables within a model had comments enclosed between /* and */ characters in triggers. (Bug #21551643, Bug #76176)
  • Generated queries were incomplete for models that included table columns of type VARCHAR with partitioning enabled. (Bug #21104120, Bug #76489)
  • Some fields within the Table Data Import wizard were misaligned and difficult to use. (Bug #20956767)
  • If the SCHEMAS tree was refreshed during a long query, MySQL Workbench became unresponsive until the query finished. (Bug #20896682, Bug #76594)
  • An error message was displayed when the delete operation was performed on an existing connection in the Manage Server Connections window. (Bug #20652117, Bug #76153)
  • The mouse pointer did not always change shape to match the area it was moved to within the visual SQL editor. (Bug #20588048, Bug #75993)
  • A complex IF, ELSEIF, ELSE structure when used to create a stored procedure within the new procedure – Routine tab produced a syntax error message as clause 45 was added and for each clause that followed. (Bug #18972055, Bug #72991)
  • Code completion did not provide a suggestion reliably for instructions included in the server dictionary, such as statements or system variables. In addition, types like TIMESTAMP were completed with the wrong type values. (Bug #18445589, Bug #27386829, Bug #89222, Bug #26897612, Bug #87907, Bug #18871688, Bug #72812)
  • Attempting to access the MySQL Enterprise Backup interface caused MySQL Workbench to stop working. (Bug #18019469)
  • An on-screen label with inaccurate text was corrected. (Bug #16808557)
  • Erroneous input at the beginning of the line in the SQL editor generated an error marker that continued to display after the wrong input was corrected or removed. (Bug #13820997, Bug #64481)
  • Popular Windows themes did not always render as expected, especially when color themes were selected on Windows hosts. In particular, some areas persisted a white background regardless of the setting. (Bug #11760110, Bug #52485)
  • When out-of-range index, unique index, or primary key values were define in the source, no warning was provided to indicate that the code produced could not be executed by the MySQL server. (Bug #11745588, Bug #17509)

New in MySQL Workbench 6.3.10 (Nov 18, 2017)

  • Bugs Fixed:
  • Performance information within the Administration – Dashboard tab demonstrated a slow rate of refresh on hosts running macOS High Sierra. (Bug #26921498)
  • Tooltips within the Administration – Dashboard tab did not display when the mouse pointer was paused over each performance graph and the host was running macOS High Sierra. (Bug #26921467)
  • Table objects did not display with the Show Selection button during the migration process on hosts running macOS High Sierra. As a result, source objects could not be selected for inclusion or exclusion. (Bug #26921431)
  • Queries executed with the Limit Rows value set to “Don't Limit” did not display rows in the result grid on hosts running macOS High Sierra. (Bug #26921372)
  • Executing a query in MySQL Workbench on a host running macOS High Sierra failed to load the result grid completely, which prevented result data from appearing within the Result Grid tab. (Bug #26826418, Bug #87714)
  • Performing a keyword search in the EER Diagram Editor on hosts running macOS High Sierra caused MySQL Workbench to exit unexpectedly. (Bug #26428849, Bug #87020)
  • Forward engineering a physical database design did not operate as expected on hosts running macOS High Sierra. (Bug #25979928, Bug #86146)

New in MySQL Workbench 6.3.9 (Feb 7, 2017)

  • Functionality Added or Changed:
  • Support was added for many MySQL 8.0 features. Note that configuration-file support for MySQL 8.0 is not available and a warning banner is displayed during attempted use. (Bug #24908593, Bug #83422)
  • With MySQL 5.7, several new instruments were added to the performance section including the following for Memory Usage: Total Memory, Top Memory by Event, Top Memory by User, Top Memory by Host, Top Memory by Thread, User Resource Usage, and the following for User Resource Usage: Overview, I/O Statistics, and Statement Statistics. (Bug #21491775)
  • With MySQL 5.7, GTID_MODE can now be set online. (Bug #20712931)
  • Workbench is now aware of the innodb_optimize_point_storage option that was added in MySQL Server 5.7.5, and later removed in MySQL Server 5.7.6. Note that MySQL Server 5.7.9 was the first 5.7 GA release. (Bug #20661496)
  • Mroonga storage engine support is now available for tables. (Bug #20058280, Bug #74367)
  • A new DDL tab was added to show the complete create statement of a table or view. Click the table inspector (info) button next to the table or view in the Schemas Navigator to display the new information. (Bug #19889537, Bug #74554)
  • Dropped support for DBDesigner 4.
  • Dropped Fabric support.
  • Dropped support for MySQL 5.1. Minimum version is now MySQL 5.5.
  • Changed to C++11.
  • Changed to GTK 3 on Linux.
  • OS X: Version 10.7 (Lion) and 10.8 (Mountain Lion) support was dropped. Now supporting 10.9 (Mavericks), 10.10 (Yosemite), 10.11 (El Capitan), and 10.12 (Sierra).
  • Windows: Zip packages and 32-bit binaries are no longer published. The .NET Framework version 4.5 is now required.
  • Linux: Fedora 23 support dropped and Fedora 25 support added. Oracle Linux 6 support was dropped.
  • The option to specify an alternative application data directory, instead of the default location, was added.
  • The JSON editor was improved with better parsing and error checking.
  • A new Log Level preference (under Others) was added to alter the log verbosity level.
  • As before, this can still be set by passing in the log-level command-line argument into Workbench at runtime, and doing so overrides the Log Level setting.
  • The bundled sakila_full.mwb model now uses a dedicated 5.7 version to allow for 5.7 specific features, regardless of the version setting in the preferences.
  • Full MySQL 5.7 language support was added, which affects grammar, syntax highlighting, preferences, behavior, and more.
  • The Home screen was modified: the connections, models, and starters were split into individual pages.
  • Bugs Fixed:
  • With multiple tabs open in the SQL Editor, using the context-sensitive menu to close all other tabs caused MySQL Workbench to exit unexpectedly. (Bug #25466086, Bug #84643)
  • Objects sorted in the schema inspector and then selected for an operation, such as Drop Table, generated a statement for the wrong object. (Bug #25464011, Bug #84697)
  • MySQL Workbench supports the option to require a CA certificate or identity validation. (Bug #25408639)
  • If a full backup added warning messages to the backup log file, then running an incremental backup later failed. (Bug #25315796)
  • No JSON tab appeared for the Open Value in Editor command if the field contained an empty array. (Bug #25222455, Bug #84106)
  • Schema names were not escaped properly in resulting DROP TRIGGER statements when a trigger was created or edited. (Bug #25036458, Bug #83655)
  • In some cases, executing a query caused MySQL Workbench to become unresponsive when the host was macOS Sierra. (Bug #25036263, Bug #83658)
  • Having a single quotation mark (') in the text field of a table caused the MySQL Schema Transfer wizard to fail. (Bug #24978403, Bug #83616)
  • Simple and complex queries executed from SQL Editor failed to complete and return control to MySQL Workbench. This behavior was observed for both local and remote queries and was often intermittent. (Bug #24977018, Bug #82951)
  • Deleting rows while connected to a remote server caused the connection to fail and for MySQL Workbench to exit unexpectedly. (Bug #24947899, Bug #81019)
  • The Selected schema drop-down list in the New Schema Privilege Definition dialog failed to display newly added schema names unless MySQL Workbench was restarted. (Bug #24798254, Bug #83111)
  • The bundled OpenSSL library was upgraded to version 1.0.2J. (Bug #24753390)
  • Tooltips failed to operate properly in the Visual Explain panel. (Bug #24577687, Bug #82816)
  • Deleting selected rows from the Result Grid caused MySQL Workbench to become unresponsive. (Bug #24411733, Bug #82466)
  • Connecting to the server resulted in the following exception: Parameter is not valid. (Bug #24394987)
  • Queries returning more than 1000 rows on an SSH connection to AWS failed and caused MySQL Workbench to become unresponsive. (Bug #24330588, Bug #82291)
  • Adding a password with the Store in Vault option caused Workbench to fail and exit. (Bug #23987798, Bug #82190)
  • Opening a saved .mwb model file with MySQL Workbench generated the following error intermittently: Error unserializing GRT data string too long. The same file, when opened directly from the file system, started MySQL Workbench and displayed the model correctly. (Bug #23857478, Bug #80017)
  • Query statements executed from the SQL Editor did not remain selected when the focus returned to the query area. (Bug #23760790, Bug #79580)
  • The schema navigator incorrectly opened a previously viewed database, instead of the one selected, after the schema filter in the Navigator panel was used to find and list multiple databases. (Bug #23760745, Bug #71699)
  • Selecting TCP/IP over SSH for existing or new connections caused MySQL Workbench to fail and exit. (Bug #23743373, Bug #82113)
  • Changes made with the Options File editor were committed to my.cnf correctly, but also generated an error. (Bug #23741731, Bug #82102)
  • Stored procedures containing valid CASE statements reported syntax errors when created or edited. (Bug #23617646, Bug #81932)
  • Graphs in the performance dashboard reported negative values when the server instance was stopped and restarted during the analysis. (Bug #23103677, Bug #81067)
  • The Migration Wizard successfully migrated the schema, but failed to migrate the data, when the data source was SQL Anywhere 16 using ODBC. (Bug #22987681, Bug #79140)
  • Selecting too many tables when attempting to reverse engineer an EER diagram caused MySQL Workbench to fail and exit. This fix sets the permitted threshold to 1000 objects and displays a warning message when the number of objects exceeds the threshold. (Bug #22828056, Bug #80516)
  • The import operation failed to import valid CSV files. (Bug #22817059, Bug #80472)
  • New connections configured with the Standard TCP/IP over SSH connection method failed and caused MySQL Workbench to become unresponsive or to exit. (Bug #22728573, Bug #80359)
  • EER diagram tables were locked to a fixed location in the window for some .mwb files. This fix enables users to unlock the tables within the diagram and to persist those changes by first changing the size of the diagram (click Model, Diagram Properties and Size) and then saving the file. (Bug #22722596, Bug #71533)
  • Performance reports generated by the Export button did not enclose in quotes and escape any string values in the CSV file, making it difficult to read the output when the strings contained commas. (Bug #22700858)
  • Check for Updates from the Help menu failed to detect new releases. (Bug #22578656, Bug #80074)
  • The Filter Rows value set in the Result Grid of a query was not reapplied when the query was changed or refreshed. (Bug #22566018, Bug #80050)
  • When running large queries over an SSH tunnel, MySQL Workbench became unresponsive. (Bug #22494755, Bug #79840)
  • The Export Data operation emitted an unhandled exception when the user connecting to the server lacked privileges on the mysql schema, but had full privileges on the database identified by the operation. (Bug #22478388, Bug #79807)
  • Adding or editing fields in the Table Templates window for a user-defined template caused MySQL Workbench to fail and exit. (Bug #22449752, Bug #79721)
  • Data exported from the Inserts tab of a table in an EER diagram generated invalid JSON syntax. (Bug #22381735, Bug #79673)
  • Some GRANT statements were parsed incorrectly. (Bug #22370783)
  • The Audit Inspector failed to initialize in MySQL Workbench when the locations of the audit log file and data directory were different. (Bug #22277384)
  • GEOMETRY table data failed to export properly into CSV file format and failed to export at all into JSON file format (with an error). (Bug #22269646)
  • Stopping a query before it finished executing often caused MySQL Workbench to stop working. (Bug #22071120, Bug #78881)
  • The placeholder row (last row of the Result Grid with NULL values) was hidden when new rows were inserted and applied. (Bug #22065173, Bug #78294)
  • Saving a reverse-engineered model caused MySQL Workbench to fail and exit. (Bug #21980722, Bug #78357)
  • The cost and data process information added to "EXPLAIN JSON" in MySQL Server 5.7.2 can now be viewed in Workbench. (Bug #21848024)
  • The autocomplete feature did not offer suggestions as expected. The CTRL+SPACEBAR keyboard shortcut can be used to activate this feature. (Bug #21685267, Bug #78185)
  • Some help text was hidden from the Schema Editor in the EER Diagram. (Bug #21630661, Bug #78021)
  • When MySQL Workbench performed a copy-back restore operation, it reported incorrectly to the mysqlbackup log that a copy-back-and-apply-log operation was performed. (Bug #21496475)
  • The require_secure_transport system variable that was added in MySQL Server 5.7.8 is now supported and can be modified using MySQL Workbench. This variable enables administrators to require all client connections to the server to be made using some form of secure transport. (Bug #21484632)
  • A dialog showing the wait time of an attempted connection now displays earlier for improved visibility. (Bug #21264710)
  • Some routine database operations caused MySQL Workbench to fail and exit intermittently. (Bug #21231450, Bug #77286)
  • The slash character (/) when used in the name of a new connection separated a group from the real connection name by default without first notifying the user. This fix gives the user an option to keep the slash character and create a connection group or to replace all slash characters in the connection name with underscore characters. (Bug #21158191, Bug #77175)
  • In a query, UNION and UNION ALL statements that contained data from different tables or different databases returned data in the Result Grid that could be edited and applied to the wrong table. This fix returns read-only data that cannot be edited directly for such queries. (Bug #21046384, Bug #76964)
  • The identifier quote character (`) was missing from the DROP statement when an attempt was made to drop the existing trigger on a database with an illegal character in the name. A syntax error resulted. (Bug #20978108, Bug #76869)
  • The property values of a table in an EER diagram could not be edited from the Properties Editor. (Bug #20930134)
  • Stored procedures containing valid query syntax produced syntax errors. (Bug #20929172, Bug #76761)
  • Some characters could not be inserted into cells of the result grid and displayed the following text-truncation error message: Inserted data has been truncated as the control's limit was reached. Please use the value editor instead for editing such large text data. (Bug #20927915, Bug #76760)
  • SQL Editor did not permit the use of DUAL in a derived-table subquery. (Bug #20800341)
  • When the resultset grid in SQL Editor was set to a font type and size that exceeded the default row height, the output from a query hid a portion the row content instead of increasing the row height to accommodate the font value. (Bug #20794106, Bug #76520)
  • The binlog_group_commit_sync_delay and binlog_group_commit_sync_no_delay_count options that were added in MySQL Server 5.7.5 are now supported, and can be modified using Workbench. (Bug #20712947)
  • Russian language connection names failed to load and display properly in the home screen. (Bug #20697403, Bug #76015)
  • The innodb_page_size MySQL Server system variable can now be changed to either 32k or 64k in Workbench, in addition to the current options. Support for these larger innodb_page_size values was added in MySQL Server 5.7.6. The default value in MySQL 5.7 is 16k. (Bug #20661249)
  • Executing the current statement of a query by using the CTRL+ALT+ENTER keyboard shortcut (Vertical Text Output) partially or fully hid the output. (Bug #20573658, Bug #75959)
  • 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 (to the left) of the closed tab. (Bug #20351753, Bug #75490)
  • A valid server connection was required before a script or model file could be viewed or edited. (Bug #20326028, Bug #75452)
  • Starting MySQL Workbench from the command line with an optional argument of a script or model file required the absolute (or fully qualified) path name of the file. (Bug #20268606, Bug #75305)
  • SQL Editor identified syntax errors in valid statements that executed properly. (Bug #20116982, Bug #74183)
  • Font sizes were increased in the Home screen for improved readability. (Bug #19982157, Bug #74721)
  • The MySQL Table Editor did not display the name of a selected table within an EER diagram when the editor was first opened. (Bug #19693466, Bug #74102)
  • Because the sys schema is installed by default as of MySQL server 5.7.7, MySQL Workbench now checks for and uses it. Otherwise, MySQL Workbench (as it has since 6.1) provides the option to install it.

New in MySQL Workbench 6.3.7 (Jun 13, 2016)

  • Functionality Added or Changed
  • Bugs Fixed
  • Functionality Added or Changed
  • The Default target MySQL version model preference is now an open text field instead of a dropdown select box. For example, rather than choosing a version such as "5.7", you can now enter a specific version such as 5.7.12. (Bug #23080421, Bug #81023)
  • Bugs Fixed
  • A typo was fixed on the Configure Server Management page. (Bug #23534786, Bug #81738)
  • On OS X, after creating a new model, and new diagram, right-clicking on the empty diagram background would freeze Workbench. (Bug #23512126)
  • Executing Data Import/Restore would emit an unhandled exception with Import from Self-Contained File enabled. (Bug #23505226)
  • On Linux, the Table Data Export wizard failed to complete the export process. (Bug #23477814)
  • The MySQL Enterprise Backup Restore functionality could emit an unhandled exception under some
  • circumstances. (Bug #23472573)
  • Editing a remote MySQL options file via the Options File management tool would emit an unhandled
  • exception after clicking Apply. (Bug #23307191)
  • Exporting data to JSON was exporting NULL values as NULL instead of null, thus breaking the JSON
  • output. (Bug #23241155, Bug #81331)
  • Under Users and Privileges, Workbench did not allow hyphens for host names in the "limit to hosts matching" field. (Bug #23224606, Bug #81301)
  • When viewing the code for an existing view (SQL to create the view), hexadecimal values were truncated. (Bug #23187761, Bug #81208)
  • Migrating a MySQL source to a MySQL target database would fail for tables that had generated columns, as the target server rejected attempts to insert data into generated columns. (Bug #23128380, Bug #81100)
  • Selecting "5.7" from Default target MySQL version did not take into account changes to newer versions, as 5.7 behaved like 5.7.0 instead of a newer version. For example, it was not possible to use the JSON data type for variables inside the stored procedure editor as JSON was added in MySQL 5.7.7. (Bug #23080421, Bug #81023)
  • The Schema filter was slow (poor performance) when a lot (1000+) of schemas were present. (Bug #23047787, Bug #80946)
  • The database migration wizard database field was described as "Leave blank to select it later" but this text was updated to read as "Cannot be blank" because it is a required field. (Bug #22896342)
  • The generated SQL generated by the forward engineering wizard would incorrectly output "VIRTUALCOMMENT" instead of "VIRTUAL COMMENT". (Bug #22880159, Bug #80618)
  • An new option is available to specify a path to the SSH configuration and/or known hosts file. This option overwrites the defaults. (Bug #22866791, Bug #80605)
  • Workbench's Alter Table functionality did not behave correctly when a column was defined using a TIMESTAMP with fractional seconds, such as TIMESTAMP(1). In this case, some columns would be hidden from the editor. (Bug #22839982, Bug #80547)
  • Under Reverse Engineering, the information provided in the wild card description to select objects contained a typo. (Bug #22828056, Bug #80516)
  • After successfully executing the database migration wizard, executing it a second time required Workbench to be restarted. (Bug #22811588, Bug #80479)
  • When executing Data Export using a remote MySQL connection, the error resulting from a missing mysqldump binary was unclear. (Bug #22753693, Bug #80240)
  • The PostgreSQL migration wizard could fail to migrate PostgreSQL databases that were generated with tryton. (Bug #22747525, Bug #79217)
  • The Dashboard and Server Status reported different Select per second values. The Server Status page reported incorrect (inflated by about 3x) values. (Bug #22739583, Bug #74822)
  • The PostgreSQL migration wizard could fail with an "pg_catalog.pg_enum does not exist" error. (Bug #22738451, Bug #71121)
  • The Workbench interface would incorrectly orient itself to display as Right-To-Left (RTL) when a system's language is set to a RTL language, despite Workbench not being translated to that language. (Bug #22722701, Bug #72126)
  • Attempting to test custom connection details (a connection not yet created by Workbench) caused Workbench to fail and exit. The Test Connection functionality only functioned for existing or new connections. (Bug #22698924, Bug #80325)
  • The "Limit to Hosts Matching" field in the user manager would incorrectly report a "Host name contains incorrect characters" error if the host named contained numeric characters. (Bug #22670269)
  • Import and export to JSON format failed if the table had column names that were keywords such as key or value. (Bug #22668918, Bug #80272)
  • The Alter Table functionality did not detect a default value change from no default value to an empty string. In other words, adding a default value of "" resulted in Workbench reporting "No changes detected". (Bug #22664805, Bug #80267)
  • The DBMS connection keep-alive interval option did not function properly. As a result, Workbench could lose the connection and result in errors similar to "Error Code: 2013. Lost connection to MySQL server during query". (Bug #22642241, Bug #80225)
  • All generated paths now will use "/" as the directory separator in order to avoid the "\s" being interpreted as a space, such as "C:\path\to\certs\server-cert.pem" for generated SSL certificates. (Bug #22636645, Bug #80087)
  • Importing CSV data with from a properly UTF-8 encoded source would sometimes fail, and instead could result with errors such as "'ascii' codec can't encode character u'\xcf' at position 29: ordinal not in range(128)". (Bug #22635390, Bug #80205)
  • With Fabric, Workbench cached the topology information and did not update it when the topology changed, like when switching to a new master. (Bug #22601466)
  • Code completion has been further improved to only show relevant details, such as if a table is referenced in the FROM clause then only show columns from that table and not all from the default schema, and entries have been reordered to show columns first (only preceded by keywords). (Bug #22579426, Bug #80092)
  • Some stored procedure definitions were incorrectly reported as having invalid syntax. (Bug #22552958, Bug #80007)
  • Executing Alter Stored Procedure with a user lacking SELECT privileges would crash MySQL Workbench. (Bug #22509047, Bug #79871)
  • With the MySQL Firewall plugin enabled, having a user name containing a single quote character (rare, but not illegal) the queries would fail and produce an error in the Users and Privileges area of Workbench. These checks are now properly escaped. (Bug #22468850)
  • With the validate_password plugin enabled, when Workbench attempted to check the strength of a new password by sending a query to the server, the password was not properly escaped in this query. In such cases, the password was incorrectly reported as a strong or weak password. The associated "SELECT VALIDATE_PASSWORD_STRENGTH" query is now properly escaped. (Bug #22468332)
  • Some internal Workbench queries failed to execute with sql_mode set to ANSI_QUOTES. (Bug #22464406)
  • The Total Time field within the Recent Activity grid of the Online Backup / MySQL Enterprise Backup section of Workbench showed an incorrect duration value. (Bug #22462974, Bug #73499)
  • With MySQL Server 5.5 and lower, executing Alter Table on tables with partitions would fail with an error similar to "Syntax error: 'PARTITION' (identifier) is not valid input at this position". (Bug #22453898, Bug #79734)
  • MySQL Workbench lacked a CentOS profile, so could fail to make remote connections to a CentOS machine. (Bug #22453095, Bug #72205)
  • After opening the stored procedure editor from the object browser, clicking Execute would execute a query that did not take into account the IN parameters. (Bug #22378620)
  • On Windows, the "DEFAULT NULL" value could unintentionally be removed from the "Alter Table" window when clicking on it. (Bug #22375946, Bug #79661)
  • The Database Migration migration link on the home page was not functioning immediately after a successful migration. (Bug #22271448)
  • Several grammar and spelling corrections were implemented into the GUI. (Bug #22251496, Bug #79373)
  • Under certain circumstances, sub-queries were reported as syntax errors. (Bug #22251347, Bug #79371)
  • Several SQL Server 2014 database migration improvements. (Bug #22243141, Bug #79299)
  • While modeling, pressing the Enter key while editing a document's properties would close the document properties window instead of adding a new line. (Bug #22204168)
  • When copying tables, Workbench makes one connection at the start to disable triggers, makes a separate connection to do the data copy, then returns to the first connection to re-enable triggers. If the copy takes longer than the server's wait_timeout, the first connection timed out. (Bug #22190703, Bug #79242)
  • The Driver sends Unicode data as UTF-8 advanced database migration option that is available when using an ODBC driver is now disabled by default. Also, connections could hang when this option was enabled. (Bug #22149342, Bug #76382)
  • Executing Delete Row(s) after selecting more than six rows from the results grid would not delete all of the selected rows. (Bug #21909625, Bug #78560)
  • Adding a DATETIME with precision (such as DATETIME(3)) from the Table Editor would eventually get reverted to DATETIME (without precision). (Bug #21666012, Bug #78153)
  • The search (magnifying glass) icon in the schema search field was misplaced after the left sidebar was resized. (Bug #21329109, Bug #77507)
  • Workbench will now prompt to continue the execution of operations containing loops in stored procedures, instead of just canceling it after ~200 executions. (Bug #21310357, Bug #77470)
  • The Performance Schema installation procedure in Workbench failed to check user privileges before attempting the installation. For example, if the user had all privileges except "ALTER ROUTINE", it would update sys.version but fail to complete the installation, and also fail to back out thereby leaving the sys.version as current but none of the functions were updated. (Bug #21261239, Bug #77360)
  • On Linux and OS X, the Options File viewer shortened (cut) long option names in the GUI, although editing their values changed the correct options. (Bug #21167521, Bug #77179)
  • MySQL connections were leaked when connecting and disconnecting to MySQL databases. It leaked one connection per re-connect to a database. (Bug #20996606)
  • A large database caused the size reported under the Schema Inspector to wrap around and display a negative number. (Bug #20990435)
  • From the Options File management feature, clicking Discard with the Advanced tab open would always revert the thread_handling option value to "one-thread-per-connection" even if it was set to "no threads". (Bug #20956570)
  • The print preview icon dialog was missing the Workbench icon. (Bug #20309812, Bug #75422)
  • Changes to the modeling Appearance font preference did not save properly, or have an effect. (Bug #20196073, Bug #75173)
  • On Windows, the Query Stats graph would not render with MySQL Server 5.7. (Bug #20141414, Bug #75100)
  • The Query Stats information tab was populated even when the Performance Schema was disabled. (Bug #20141262, Bug #75101)
  • The Toggle whether execution of SQL script should continue after failed statements button was updated to better indicate when the option is enabled or disabled. (Bug #20093801, Bug #74982)
  • On Windows, after closing and reopening Workbench with several SQL Editor tabs open, the tabs names were hash values (instead of MySQL connection names) if the connection names contained non- standard text. (Bug #20086117, Bug #74966)
  • In the Table Editor, if a column has NN checked, and NN is then unchecked, then a default NULL value is automatically added to the CREATE TABLE statement when Apply is clicked. The column then shows a default value of NULL in the Table Editor. (Bug #19890571, Bug #74558)
  • If a setting is (incorrectly) defined twice in my.ini, Workbench separates its values with a newline ("\n"). For example, if sort_buffer_size is defined twice, Workbench displays it as "sort_buffer_size=256K \n256K". Workbench now follows MySQL Server behavior, and uses the last defined option. (Bug #19769849)
  • The cursor could seemingly disappear after executing a query, as it could remain at its last position when the query started to execute. (Bug #19703074, Bug #74128)
  • The model Page setup... functionality was not always preserved when choosing a size for printing. (Bug #11766583, Bug #59724)

New in MySQL Workbench 6.3.6 (May 4, 2016)

  • Functionality Added or Changed:
  • On OS X, the multiple object selector was disabled in the model overview. (Bug #22265928)
  • On Linux, Fedora 23 is now supported. (Bug #22146526, Bug #79101)
  • The "mysql_old_password" protocol is no longer supported by Workbench, as its support was removed in MySQL Server 5.7. (Bug #22093548, Bug #78947)
  • Management operations when using an SSH MySQL Server connection that authenticated using a password (and not SSH keys) would not function. (Bug #22047602)
  • The File, New Query option no longer requires an open MySQL connection. (Bug #21879064)
  • The MySQL Firewall tab is now disabled when the Firewall user is being created. (Bug #21150265)
  • Bugs fixed:
  • The results grid remained empty after executing SELECT queries. A new GTK2 prerequisite was added, which is checked by the Yum repository. This affected Enterprise Linux variants, such as the Oracle Linux and CentOS distributions.
  • This fix was released (pushed) after version 6.3.6 was initially released. Current users of 6.3.6 must reinstall Workbench. (Bug #22376818, Bug #79495)
  • Setting the MySQL Firewall mode to "PROTECTING" for a user without defined rules would emit an unhandled exception. (Bug #22294174)
  • Improvements were made to the Microsoft SQL Server 2008 migration wizard. (Bug #22271597)
  • On OS X, the MySQL Firewall management option was missing from the commercial edition builds. (Bug #22270244)
  • After editing the code of a routine and closing the routine editor, the changed routine was duplicated instead of applying the changes to the original routine object. (Bug #22269199)
  • The JSON Data Field Value Editor functionality was improved, and bugs were fixed. Workbench 6.3.5 had known limitations. (Bug #22265214, Bug #22337871)
  • On Linux, the MySQL Firewall installation checked the path /usr/share/ instead of /usr/share/mysql/. (Bug #22263249)
  • For Online Backup, the Fix Grants for MEB function would not create the MySQL Enterprise Backup user account. (Bug #22258080)
  • The SSL results page listed the "-" character as "_" for the SSL certificate file names. (Bug #22243210)
  • Exporting a database from the Data Export wizard did not function with remote connections. (Bug #22233795)
  • The libzip library was updated; Workbench can now be installed on Ubuntu 15.10. (Bug #22230416, Bug #79320)
  • After initially altering a table using the Alter Table, subsequent alterations to the same table in the same screen, without having closed the screen, would not always complete, as the previous alterations were applied again. For example, it might attempt to add a column that was already added, or remove a column that was already deleted. (Bug #22202325, Bug #79265)
  • Workbench did not recognize identifiers with a leading digit if it was preceded by a dot. (Bug #22193758, Bug #79247)
  • After creating a table, editing the table in the same tab would yield an error after clicking Apply. (Bug #22178996, Bug #79199)
  • Clicking Apply a second time while performing an Alter Table operation would emit a "No Changes Detected" message, despite changes being present. (Bug #22169405, Bug #79164)
  • The MySQL connection search field's background and text were both white, making it difficult to decipher. (Bug #22168697, Bug #79159)
  • On Windows 10, and with resolutions of 1366x768 and below, the default table editor window did not show the table columns.
  • As a workaround, the output pane could be resized or hidden. (Bug #22168049, Bug #79160)
  • The "BY" keyword is now supported. (Bug #22151204, Bug #79121)
  • The MySQL Enterprise Backup binary can now be configured per MySQL connection, to match the correct version needed by the connected MySQL server. Before, only one MySQL Enterprise Backup binary could be used for all connections. (Bug #22143844, Bug #79108)
  • Compiling Workbench now requires Connector/C++ 1.1.7 or higher, as this is the first Connector/C++ release that supports JSON. (Bug #22141269, Bug #79054)
  • On the Server Logs management tab, the Copy and Copy Details options were switched. (Bug #22139172, Bug #79082)
  • The Error Logs management tab showed a MySQL Firewall button within the community edition. (Bug #22139172, Bug #79082)
  • Attempting to install MySQL Enterprise Firewall would fail with the following error: "Unhandled exception: type object 'FileUtils' has no attribute 'check_file_readable'".
  • As a workaround, execute a xyz_install_firewall.sql script that is bundled with MySQL Server. (Bug #22138989, Bug #79083)
  • The Alter Table tool did not function with partitioned tables. (Bug #22135172, Bug #79070)
  • The preference windows could not be resized. (Bug #22121297, Bug #79022)
  • The USE statement result was not preserved in the SQL editor, which sometimes led to unknown errors when executing multiple statements. (Bug #22106190, Bug #78985)
  • After placing a new table on an EER diagram, and double-clicking on the new table, the column fields were hidden. (Bug #22090203, Bug #78931)
  • "ALTER PROCEDURE" changes were not detected by Workbench 6.3.5.
  • As a workaround, the SQL Editor could be used to decorate the "CREATE PROCEDURE" code with delimiters. (Bug #22084956, Bug #78924)
  • Workbench 6.3.5 would fail to export MySQL Server 5.6 and below, due to changes present in MySQL Server 5.7.
  • As a workaround, a MySQL 5.6 version of mysqldump could be used. (Bug #22060729)
  • The modeling table editor did not list the JSON data type in the dropdown select list, nor did it accept it manually. Importing a JSON column from a live database worked, but creating/assigning the JSON type in the editor was not possible. (Bug #22060699, Bug #22116098, Bug #79012)
  • Reverse Engineering a database that contained JSON data (columns) failed, and crashed Workbench. (Bug #22053512)
  • The Validate option was missing from the JSON field value's editor. (Bug #22052957)
  • The Grid and Tree tabs would interfere with each other in the JSON Data Field Value Editor. (Bug #22052934)
  • When using a remote connection, clicking the wrench icon next to a table name in the object browser would cause a crash. (Bug #22052557)
  • From Models, Create EER Model From Script, importing a script would close the diagram instead of creating the model. (Bug #22048218)
  • The MySQL Firewall installation wizard did not function. (Bug #22047561)
  • The data migration wizard did not always function with BLOB data. (Bug #22046141)
  • On Linux, with the commercial edition, the Online Backup log window's status log would not always update. (Bug #22027353)
  • Attempting to add comments to stored procedures would fail with invalid syntax errors. (Bug #21941439, Bug #78683)
  • The Action Output auto-scrolling failed to function after clicking inside the action log. (Bug #21930774, Bug #78648)
  • The Table Data Import wizard failed to import large integers. They are now properly detected and assigned as BIGINT. (Bug #21896324)
  • Whitespace is now trimmed from the MySQL Connection fields. (Bug #21865018, Bug #78471)
  • The MySQL Server start and stop management operations would generate unhandled exceptions. (Bug #21861171)
  • With MySQL Server 5.7.8+ connections, the login name (username) can now be 32 characters in length. (Bug #21848065)
  • The Copy All Field Names action would insert extra (repeated) column names. (Bug #21760124, Bug #78280)
  • The SYS Schema could not be installed using a remote MySQL Server connection. (Bug #21661235)
  • The SHOW GRANTS statement would be seen as invalid syntax. (Bug #21520434, Bug #77868)
  • Generated columns(a feature added in MySQL 5.7) were not fully supported in the SQL editor, Table Editor, nor Modeling interface. (Bug #21505058, Bug #77837)
  • The bundled OpenSSL library was upgraded to version 1.0.1p. (Bug #21438134)
  • When adding stored procedures to a Routine Group, Workbench would sometimes append "_SYNTAX_ERROR" to the procedures. (Bug #21174637, Bug #77197)
  • Several behavioral improvements were made to Workbench for when the MySQL Server connection is down. (Bug #21131790)
  • SQL auto-completion would sometimes show unavailable columns. (Bug #21046868, Bug #76954)
  • MySQL Workbench sometimes wrongly detected a syntax error when creating stored procedures in the SQL editor. (Bug #21031036, Bug #76934)
  • Including a model (via File, Include Model) generated a window that was too small. (Bug #20956593)
  • When editing a MySQL Server connection, pressing Enter under Server Connection, Advanced, Others, could shutdown Workbench. (Bug #20930014)
  • On Windows, the Vertical Output tab failed to close. (Bug #20834266, Bug #76590)
  • The performance_schema_max_sql_text_length and max_digest_length options were not displayed under the Options File tab. These variables dictate how queries under Statement Analysis are truncated. (Bug #20671061, Bug #76223)
  • Resizing the New Job window in the Online Backup management tool would show a floating text box. (Bug #20631601, Bug #76110)
  • On Fedora 21, Locate Log Files and Show Log File did not function due to an underlining Fedora 21 glib issue. (Bug #20609499, Bug #76066)
  • On OS X with multiple displays present, the SQL auto-complete box would always show on the main display, even if Workbench was on the secondary display. The underlining Scintilla library was updated to solve this problem. (Bug #20341650, Bug #75460)
  • Workbench would report SQL syntax errors for subqueries using multiple parentheses. (Bug #20330840, Bug #75462)
  • Saving a model file with non-ASCII characters in the name would crash Workbench, and renaming a file using non-ASCII characters would rename the file using the .bak file extension. (Bug #20328493, Bug #75455)
  • On Windows, the MySQL Workbench application is now associated to files with the .sql extension. (Bug #20326058, Bug #75453)
  • Scheduled incremental backups would not function if the file path contained spaces. (Bug #20254772, Bug #75092)
  • The Check for Update functionality did not detect newer Workbench versions for the commercial edition. (Bug #20167571, Bug #75132)
  • With incremental backups, TTS usage was attempted with the Use Transportable Tablespaces option disabled. This resulted in an error. (Bug #20098272)
  • Workbench's Alter Table functionality did not detect changes to fractional seconds. (Bug #19774377, Bug #74254)

New in MySQL Workbench 6.3.5 (Oct 21, 2015)

  • Known limitations:
  • The new JSON editor is in an early state, and has a number of usability issues
  • The table editor in a MySQL Workbench model does not allow the JSON data type. The table editor in the SQL Editor is not affected
  • Model synchronization fails to function for tables with JSON columns
  • The MySQL migration wizard will not function with MySQL Server 5.7 as the source database. However, MySQL Server 5.7 can be the target database
  • Creating a MySQL Server 5.7 dump does not function properly
  • Functionality Added or Changed:
  • A JSON viewer/editor was added in the field editor for result sets.
  • Bugs Fixed:
  • Executing Create EER Model from Database with Place imported objects on a diagram enabled would not always create the diagram. (Bug #22046248)
  • On OS X 10.11, a newly opened EER diagram was not always viewable. A workaround was to either scroll or resize the EER diagram window. (Bug #22016760, Bug #78829)
  • MySQL Workbench commercial edition now checks MySQL Enterprise Backup compatibility with MySQL 5.7 when using the Online Backup and Restore features. MySQL Enterprise Backup 4.0 and above is required with MySQL 5.7 and above. (Bug #21972677)
  • On Windows, connecting via RDP to Workbench with a model would cause MySQL Workbench to crash. (Bug #21951171)
  • On Windows with the firewall enabled, either editing a current user or creating a new user from the Users and Privileges tab would crash after clicking Apply. (Bug #21866290)
  • Under Server Status, the reported Disk Space in Data Dir was limited to "1.00 TB", even if more space was available. (Bug #21833382)
  • The SQL parser and grammar was updated; some queries would emit bogus errors, although they would execute with success. For example, queries with syntax such as "ALTER TABLE foo MODIFY COLUMN bar VARCHAR(10)" and "ALTER TABLE foo MODIFY bar INT NOT NULL". (Bug #21776051, Bug #20116935, Bug #77549, Bug #75048)
  • On Windows, creating blocked statements (such as BEGIN...END) with auto-complete activated would cause MySQL Workbench to emit an unhandled exception (Bug #21774642, Bug #77488)
  • On Linux, dragging a routine to a Routine Group did not function. (Bug #21770594, Bug #78299)
  • Opening Open Value in Viewer to view the contents of BLOB and string types would sometimes crash MySQL Workbench. (Bug #21746985, Bug #75516)
  • An SSH timeout option was added, under the Others preferences panel. (Bug #21690190)
  • After opening a model file, after choosing Preferences, Others, checking (enabling) Allow more than one instance of MySQL Workbench to run, clicking OK would crash MySQL Workbench. (Bug #21666322)
  • On Windows 10, MySQL Workbench failed with an error similar to "The type initializer for 'HtmlRenderer.Utils.FontsUtils' threw an exception". The HtmlRenderer.dll DLL was updated with a fix. (Bug #21642135, Bug #75344)
  • Clicking Cancel when using the Table Import wizard would emit an error, although the import process continued. (Bug #21610117, Bug #78013)
  • On OS X, the Rescan for local MySQL instances operation was not discovering local MySQL server connections. (Bug #21605220, Bug #77989)
  • On Windows, and when connecting to MySQL Server 5.7.8 or higher, the Server Logs did not properly display the MySQL error logs, and it instead referred to a file named "stderr" that could not be found. This is because the error log is now written to the Windows Event Log. (Bug #21566823, Bug #77958)
  • Executing Control + W to close all tabs, and then executing it again (with all tabs already closed), would emit a Null Pointer Exception. (Bug #21543454, Bug #77906)
  • When creating new user privileges with access to All Schemas (via the % wildcard), the resulting user record in mysql.db was created with an asterisk (*) in mysql.db.Host and mysql.db.Db instead of using %, resulting in inability to connect to the database.
  • As a workaround, you could have executed queries such as "UPDATE mysql.db SET Host='%', Db='%' WHERE User = 'MyNewUserName'; FLUSH PRIVILEGES;". (Bug #21529564, Bug #77865)
  • Several grammar and spelling fixes were made in the GUI. (Bug #21526053)
  • With MySQL not running, the MySQL Enterprise Backup Restore option would emit an unhandled exception, and it was unable to execute restore operations. (Bug #21496671, Bug #21619525)
  • Expanding the schema tree for a database that contained a large number of tables, such as 20,000 tables, would cause a crash. (Bug #21490728, Bug #77801)
  • The Table Data Import wizard failed to import data into an existing table when a DECIMAL column was used. (Bug #21461807, Bug #77739)
  • Importing a DBDesigner4 schema would sometimes fail, and cause a crash. (Bug #21429693, Bug #77688)
  • After opening a model's EER diagram for the first time, opening the Preferences menu would immediately cause MySQL Workbench to crash, due to some parts being uninitialized. (Bug #21395988, Bug #77662)
  • When copying elements from one diagram to another, the style attributes were not copied, although the position of the elements were retained. (Bug #21384159, Bug #77640)
  • The Performance and Firewall options were missing from the Server menu in the commercial edition. (Bug #21379250)
  • The Unlock the Audit log procedure in the Audit Inspector would sometimes fail due to malformed XML. (Bug #21379224)
  • Sometimes Startup / Shutdown management would ignore the system's profile and use default commands to start and stop the MySQL server. (Bug #21357438)
  • On Linux, with the commercial edition, MySQL Workbench did not delete the cron job after the scheduled online backup was deleted. (Bug #21312652)
  • On Ubuntu 15.04, MySQL Workbench threw a lot of GLib-GObject warnings. (Bug #21292286, Bug #77420)
  • Forward Engineering would sometimes append "COMMENT ''" to field and index definitions. (Bug #21278452, Bug #21429688, Bug #21390162, Bug #77400, Bug #77685, Bug #77644)
  • Making an SSH connection to a server where the fingerprint was not in the known_hosts file, clicking Test Connection under Remote Management would freeze MySQL Workbench. (Bug #21264620)
  • References: This bug was introduced by Bug #21122128.
  • The Data Export wizard failed to include date information when the JSON export type was used instead of CSV. (Bug #21259942, Bug #77364)
  • With the commercial edition, setting up a new Online Backup profile would display an "Error Configuring Backup" error after entering in details, such as the MySQL Enterprise Backup executable path and backup home directory, and then clicking Ok. The settings would not save due to UTF-8 conversion failures in the mysqlwbmeb.py helper file. (Bug #21255978)
  • When importing JSON, the Table Data Import wizard would fail at the Configure Import Settings step, and emit "Can't analyze file, please try to change encoding type...". (Bug #21252834, Bug #77335)
  • After exporting a database with no-create-info checked, the import operation would fail to import it. (Bug #21250323, Bug #71393)
  • In the Table Data Import wizard, the Field Separator dropdown in the Configure Import Settings operation did not list the "," (comma) character. (Bug #21240249)
  • From the Table Data Import wizard, switching the line endings from the Configure Import Settings screen, and then switching it back, would cause the table columns to be displayed on a single line. (Bug #21240215)
  • Improved integer and number recognition for data import/export with CSV files. (Bug #21240092)
  • In the commercial edition, the Audit Log Inspector logo was broken. (Bug #21236152, Bug #77302)
  • With the commercial edition, clicking Firewall after stopping the MySQL Server would emit the following unhandled exception: "'NoneType' object has no attribute 'find'". (Bug #21236051, Bug #77304)
  • The validate_password plugin options are no longer visible in the Options File editor when the plugin is not enabled. (Bug #21187942)
  • With MySQL server not running, and with a MySQL Enterprise Backup configuration file missing, attempting to open either the Online Backup or Restore tabs would throw an unhandled exception. (Bug #21161660)
  • On Fedora, executing Help, Locate Log File / Show Log File would fail to function, due to an underlining problem with glib 2.44. For additional information, see Fedora bug #1175719. (Bug #21113811)
  • In the Audit Inspector, executing Select or Deselect from the Show Columns context-menu would fail to function. (Bug #20956668)
  • Several buttons and text boxes were not always located in the correct location. (Bug #20929972)
  • On OS X, the Shift + Alt + Arrow combination would select individual characters instead of whole words. (Bug #20797766, Bug #76526)
  • References: This bug is a regression of Bug #50085.
  • When executing Start Command Line Client, entering the incorrect MySQL password would immediately close the Window. Now, an error is displayed before the window is closed. (Bug #20737515)
  • The VARBINARY type could not be edited in the results view grid. Clicking Apply to execute the change would emit an error. (Bug #20735501, Bug #76386)
  • On Windows, SSH connections would fail when connecting to a server with pageant running. (Bug #20652700, Bug #76168)
  • The MySQL server connection would sometimes timeout (error 10060) while processing the result set when combined with a large number or rows (e.g., 10,000) and an SSH tunneled MySQL connection. (Bug #20639995, Bug #74557)
  • The Action Output query tooltip would sometimes display information about the wrong query. (Bug #20535654, Bug #75877)
  • On Windows, a scheduled incremental MySQL Enterprise Backup backup job would always choose the latest backup as the base for the backup instead of using the last successful backup. This meant that after a failed backup, future incremental backups would fail until the next successful full backup. (Bug #20533780)
  • The Catalog Tree would truncate table names at around 20 characters. (Bug #20122059, Bug #74995)
  • The Table Inspector could fail if the schema name contained a dash. (Bug #20007660, Bug #74788)
  • The bundled SSH library (paramiko) was not capable of supporting the key exchange algorithm (ecdsa) added in OpenSSL 6.7. (Bug #20003201, Bug #74658)
  • When a connection to a MySQL server instance through a SSH Tunnel, MySQL Workbench failed to recognize the server fingerprints stored in the .ssh/known_hosts file, and claimed that the server authenticity could not be established. Clicking Continue also caused the current fingerprint to be removed, after which MySQL Workbench froze.
  • Also, due to a bug in the underlining paramiko library, if a server supported ECDSA and RSA, paramiko would first try to use RSA and, as such, not use ECDSA. For information about this bug, see https://github.com/paramiko/paramiko/issues/243. (Bug #19714350, Bug #74160)
  • The import and export process did not always function with network folders. (Bug #19443451, Bug #73575)

New in MySQL Workbench 6.3.4 (Jun 15, 2015)

  • Functionality Added or Changed:
  • Added MySQL Enterprise Firewall support. For additional information, see MySQL Enterprise Firewall Interface (http://dev.mysql.com/doc/workbench/en/wb-mysql-firewall.html).

New in MySQL Workbench 6.3.3 (Apr 23, 2015)

  • Bugs Fixed:
  • On OS X, after opening the Table Data Export feature from schema sidebar in the SQL Editor, the wizard's window was not wide enough to display the wizard's controls. (Bug #20822603)
  • Executing a partial MySQL Enterprise Backup job and then clicking Configure Job would emit an unhandled exception for RadioButton_set_active. (Bug #20734865)
  • Copying SQL statements from the history panel would crash MySQL Workbench. (Bug #20724034, Bug #76362)
  • Right-clicking on an out-of-focus empty field under the Inserts editor in the EER modeling table editor would crash MySQL Workbench. (Bug #20692093, Bug #76278)
  • On OS X, inserting a new row of data via the results grid would either crash MySQL Workbench after clicking Apply, or insert the rows along with additional empty NULL filled rows. (Bug #20681539, Bug #76245)
  • The Schema Transfer Wizard would always report a failure, even when the operation succeeded. (Bug #20680466, Bug #75125)
  • Triggers could not be edited after applying changes to a different trigger. Attempting to do this multiple times could also have caused MySQL Workbench to crash. (Bug #20678160, Bug #76234)
  • While creating or altering a table, the ENUM type handler would remove parentheses and quotes. For example, "enum('One','Two')" would convert to "ENUMOne, Two".
  • Workaround: Review and correct the SQL before submitting the CREATE TABLE or ALTER TABLE. (Bug #20667788, Bug #76214)
  • Stopping a MySQL server service immediately after installing MySQL Workbench would emit an "Unhandled exception: not a string" message.
  • Workaround: restart MySQL Workbench. (Bug #20662285, Bug #76194)
  • The trigger editor would fail to save data for triggers including the BEGIN ... END construct. It would also generate a "GLib-GObject:ERROR:gsignal.c:756:emission_pop: code should not be reached" error. (Bug #20655462, Bug #76082)
  • The StrictHostKeyChecking and UserKnownHostsFile variables are now read from the SSH configuration file when using SSH for a MySQL connection.
  • MySQL Workbench will attempt to load this configuration from the following locations: For Windows, %APPDATA%\MySQL\Workbench\ssh\ssh_config or %APPDATA%\MySQL\Workbench\ssh\config. For Linux and OS X, ~/.ssh/ssh_config or ~/.ssh/config. (Bug #20653285, Bug #75764)
  • On Linux, the >Check for updates functionality reported a "Name or service not know" error when an Internet connection was not available, and now it emits "No network connection available." (Bug #20631579, Bug #76109)
  • Checking an Advanced Options checkbox under Performance Schema Setup would generate an error. (Bug #20630030, Bug #76101)
  • Executing the Table Maintenance action on a table after creating an event would fail with an "invalid column Comment for resultset" error. (Bug #20259610, Bug #75291)
  • Data could not be imported into a result set when the results did not contain a Primary Key. The new import wizard does not have this limitation. (Bug #19881191, Bug #74514)
  • On OS X, SSH tunneling would sometimes fail start. (Bug #11764879, Bug #57758)

New in MySQL Workbench 6.3.2 RC (Mar 13, 2015)

  • Bugs Fixed:
  • The icons for the data import and export features were reversed. (Bug #20645134, Bug #76143)
  • Deleting a MySQL Enterprise Backup partial backup job would generate an unhandled exception. (Bug #20637715, Bug #76129)
  • While modeling, the tables were no longer being listed in alphabetical order. (Bug #20299714, Bug #75401)
  • The Audit Log inspector no longer requires sudo access to read audit log files, and will only prompt for sudo rights if the audit log is not readable by the MySQL Workbench user. (Bug #20255637, Bug #75288)
  • The MySQL configuration file editor was missing the innodb_buffer_pool_size option. (Bug #20168131, Bug #75131)
  • While modeling, the link between two tables could not be deleted. (Bug #20123214, Bug #75064)
  • The FROM keyword was not listed in the code completion popup. (Bug #18899887, Bug #72862)

New in MySQL Workbench 6.3.1 Beta (Mar 5, 2015)

  • FAST DATA MIGRATION:
  • A new "fast migration" option was added to the migration wizard. This is another way to transfer data from one MySQL server to another while performing a migration, and it complements the existing solutions. The premise is to use a generated script on the source server to create a dump that you move to the target machine to perform the import there. This avoids the need to traffic all data through MySQL Workbench, or to have a permanent network connection between the servers. Instead, the dump and restore is performed at maximum speed by using the LOAD DATA call for the MySQL import. The migration wizard automatically creates all necessary scripts for all supported platforms and servers. The generated script creates a self-contained Zip file that must be copied to the target server. You unzip it and execute the provided script to perform the data import.
  • DB2 TO MYSQL MIGRATION:
  • Migration from the DB2 database to MySQL is now supported.
  • SSL CERTIFICATE GENERATOR:
  • A new SSL certificate generation wizard was added. This new wizard helps create proper SSL certificates for both MySQL clients and MySQL servers. Connections in MySQL Workbench are updated with the certificates by the wizard. This wizard requires OpenSSL to create the certificates. An example my.cnf / my.ini file is also generated that utilizes the generated certificates.
  • SQL EDITOR AUTO-COMPLETION:
  • The SQL editor auto-completion improvements include the following changes:
  • It now functions with all statement types, when before only SELECT statements were fully supported. 
It now minds the MySQL server version. For example, it now only shows the engines available from the server. 
Additional suggestions are now available, such as system variables, engines, table spaces, logfile groups, and more. 
New graphics including color coded (and tagged) entries. 
It is context aware, as for example it only shows available keywords, columns, and tables. 
Improved MySQL 5.7 syntax support. 
MYSQL ENTERPRISE BACKUP:
  • Profile handling now detects mismatches between MySQL Enterprise Backup executables and corresponding profiles.
  • Improved scheduling logic
  • TABLE DATA EXPORT AND IMPORT WIZARD:
  • A new table data import/export wizard was added. This feature enhances the current CSV import and export feature found in the SQL editor's result set viewer. It supports import and export of CSV and JSON files, and allows a more flexible configuration (separators, column selection, encoding selection, and more). This new wizard does not require an executed statement on a table for a result set to be operated on, as it can now work directly on tables. The wizard can be performed against either a local or remotely connected MySQL server. The import action includes table, column, and type mapping.
  • The wizard is accessible from the object browser's context menu.
  • ADDITIONAL CHANGES:
  • MySQL Fabric 1.5 is now supported. Older versions of Fabric are no longer supported due to incompatible protocol changes.
  • OS X builds were switched from 32-bit to 64-bit.
  • Platforms support changes: Fedora 21 and Ubuntu 14.10 support was added, while Ubuntu 12.10 support was dropped.
  • The bundled MySQL client library was upgraded from MySQL 5.6 to MySQL 5.7.

New in MySQL Workbench 6.2.5 (Mar 3, 2015)

  • Bugs Fixed:
  • On Windows, closing MySQL Workbench after opening the SQL editor would cause a MySQL Workbench process to hang (remain active).
  • On Linux and OS X, this instead delayed the MySQL Workbench shutdown for several extra seconds.

New in MySQL Workbench 6.2.3 (Sep 24, 2014)

  • Bugs Fixed:
  • The Set field(s) to NULL result field context-menu option did not function. (Bug #19499823, Bug #73079)
  • In the SQL editor, code completion would freeze MySQL Workbench when used with a large (1000+ tables) database. (Bug #17457790, Bug #70338)

New in MySQL Workbench 6.1.7 (Jun 30, 2014)

  • Bugs Fixed:
  • Security Fix: The linked OpenSSL library for MySQL Workbench Commercial 6.1.7 has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224.
  • This change does not affect the Oracle-produced MySQL Community build of MySQL Workbench 6.1.7, which uses the yaSSL library instead. (CVE-2014-0224)
  • Under certain conditions (with a subquery), Visual Explain would fail with the error "error calling Python module function SQLIDEQueryAnalysis.visualExplain", even when the tabular EXPLAIN was properly generated. (Bug #18997475, Bug #72725)
  • The Backup Recovery process could fail and generate an unhandled exception titled "list indices must be integers, not NoneType" after clicking Cancel. General improvements were made to this functionality. (Bug #18925451)
  • The Form Editor could generate an "Index was out of range" error after adding a new record and then clicking Add Record. (Bug #18891983, Bug #72844)
  • The schema selection step of the migration wizard would not display the complete names of the schemas nor complete the migration process if the schema name contained a dot. (Bug #18844624, Bug #72757)
  • Sometimes MySQL Workbench would crash when connecting to a remote Linux host using SSH. (Bug #18817608, Bug #72486)
  • The Backup Restore action would hang with a MySQL server running in a MySQL Sandbox environment that used MySQL Sandbox to start/stop the MySQL server. (Bug #18814560)
  • With the Move Model tool enabled, dragging a model while hovering (and pausing) over a table would generate a tooltip that would not go away. (Bug #18718801, Bug #72555)
  • Executing the following steps (in order) would generate an error: change layer name, change layer color, and then resize layer. (Bug #18760955, Bug #72647)
  • For a new EER diagram, editing a text object after adding a different text object could cause MySQL Workbench to crash.
  • A workaround was to close the new diagram and model, and then reopen the model and diagram. (Bug #18718784, Bug #72559)
  • MySQL error code 1698 (ER_ACCESS_DENIED_NO_PASSWORD_ERROR) is now handled as an authentication error. (Bug #18711142, Bug #72536)
  • After enabling Import from Folder in the Data Import / Restore wizard for a connection, doing the same for a second connection would reset (deselect) this option in the first connection. (Bug #18685308, Bug #72492)
  • A new "Override sudo command line" option was added to the connection manager under the System Profile in the connection editor for systems other than Windows. It can (optionally) configure the sudo command line to use on any operation requiring root access for administration tasks.
  • If left blank (the default), MySQL Workbench continue to pass in -S and -p. Otherwise, you can replace the default sudo command. This should only be defined if the server configuration requires it. (Bug #18679748)
  • On Mac OS X, pressing Option + Shift with the Arrow buttons did not function as expected in the SQL editor. This key combination selects adds a word (string) to the current selection. (Bug #18385643, Bug #72014)
  • When creating a table, the FULLTEXT and SPATIAL index types were not present in the index type drop-down list when non-MyISAM tables were selected. (Bug #18376840, Bug #71998)

New in MySQL Workbench 6.1.6 (May 19, 2014)

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

New in MySQL Workbench 6.1.4 (Apr 1, 2014)

  • Bugs Fixed:
  • With MySQL Enterprise Backup, validation was added when backing up schemas without tables.
  • Executing Backup recovery after a full Online backup could cause a crash.

New in MySQL Workbench 6.1.3 RC (Mar 25, 2014)

  • Functionality Added or Changed:
  • The Beautify query feature was changed. It now only affects the current statement, unless there is an explicit selection. Before, it would reformat all statements in the window by default. (Bug #18237189, Bug #71544)
  • The default schema is now expanded automatically when a connection is opened, or when the default schema changes. (Bug #18237247, Bug #70522)
  • A new Create Missing Local Connections option was added to the right-click context menu on the Home screen. It attempts to identify and create connections to locally installed MySQL servers. (Bug #17454766, Bug #70150)
  • A specific connection string can now be passed to the --query command-line option at startup, in the form of "--query user@host:port". If this connection string does not already exist, then it will be created. (Bug #17353691, Bug #70134)
  • MySQL Workbench now checks if the lower_case_table_name variable is correctly set on Microsoft Windows and Mac OS X systems. If not, then MySQL Workbench will display a dialog after connect, and emit a warning message when performing synchronization or reverse engineering actions. (Bug #14802853)
  • New Report a Bug functionality now opens a browser with the MySQL bug page pre-populated with MySQL Workbench data. This also allows MySQL Workbench to be fully manipulated while submitting the bug report. (Bug #14079590, Bug #65258)
  • Bugs Fixed:
  • The local private key file for an SSH connection when executing Remote Connection in MySQL Workbench through SSH could not be saved to a folder with accented characters. (Bug #18328846, Bug #71800)
  • FOUND_ROWS() (after a SQL_CALC_FOUND_ROWS statement) returned 1 (true) instead of the number of found rows. (Bug #18342953, Bug #71920)
  • On Linux, the audit log inspector did not function when there were not spaces in the "ls" date column. On some Linux variants, such as SLES 11, "ls -l" outputs a date format like "2014-02-14" instead of "Feb 14". (Bug #18257020)
  • On Mac OS X, the Find button was grayed out (disabled). (Bug #18290813, Bug #68949)
  • On Mac OS X, using key shortcuts to record marker positions #3 and #4 on the modeling canvas did not function, as these shortcuts (Command + Shift + 3 and Command + Shift + 4) are predefined to execute screenshot features. (Bug #18268043)
  • Exported JSON string delimiters used double quotes instead of single quotes, and the exported JSON file extension changed from .js to .json. (Bug #18314718, Bug #71846)
  • Some user interface (UI) elements explicitly set a background color but not a font color, and vice-versa. (Bug #18305958, Bug #71828)
  • The Shift + Control + Arrow Key (left or right) now moves the cursor word-by-word in the SQL code editor, to go along with the character-by-character Shift + Arrow Key functionality. (Bug #18267537)
  • A Show schema name diagram preference was added. If enabled, it shows the schema name in the table heading of an EER Diagram. (Bug #18268014, Bug #71592)
  • On Mac OS X, pressing Shift would interfere with the Option + Arrow word-by-word selector operation, and would instead change it to a character-by-character operation. (Bug #18237104, Bug #64358)
  • When migrating from Microsoft SQL Server, nVarchar(n) columns would always migrate to a MySQL VARCHAR(n) column that was twice the size. (Bug #18195599, Bug #71608)
  • While executing the Migration Wizard, successfully entered credentials during a Test Connection remained in cache until the migration tab was closed, despite the Save password in keychain option not being enabled. The connection is now closed after executing Test Connection. (Bug #18195389)
  • On Linux, Help-View Reported bugs link (to view current MySQL Workbench bugs) was broken. Its path included "WB bugs" instead of "WB bugs". (Bug #18231109, Bug #71668)
  • After copying and pasting tables within the Alter Table panel, clicking Apply would return "No changes detected" instead of detecting the changes. Copied and pasted entries (from the clipboard) are now detected and saved. (Bug #18205924, Bug #71632)
  • The Check for updates operation failed to function for the commercial edition. (Bug #18225980, Bug #16879533, Bug #69346)
  • MySQL Workbench will now see the NO ACTION and RESTRICT referential action options as two different options. (Bug #18237503, Bug #71499)
  • The values "true" and "false" are now converted to "1" and "0" if the column is a BOOLEAN or TINYINT. Also, synchronizing a BOOLEAN against a TINYINT no longer generates any differences, when before it might generate SQL that "changed" TINYINT columns to TINYINT. (Bug #18124474, Bug #71458)
  • When migrating from Microsoft SQL Server, mapping a VARCHAR column to TEXT would still attempt to migrate it to VARCHAR, which could yield an error if the VARCHAR exceeded the maximum size. It now properly maps to TEXT. (Bug #18167872, Bug #71036)
  • When migrating from Microsoft SQL Server, column names greater than 64 characters were automatically renamed with the object migration component. The schema creation created the new table structure as expected, but later the bulk migration bulk data transfer attempted to import data to the original column names. (Bug #18168027, Bug #71532)
  • The Store connection for future usage option in the Database Migration wizard did not store the defined MySQL connections. (Bug #18124149)
  • Saved connections would sometimes not function (connect) properly unless the password was saved to the local vault. (Bug #18154787)
  • When migrating from Microsoft SQL Server, DECIMAL(n, n) columns did not properly migrate to BIGINT(n). (Bug #18105487, Bug #71379)
  • When migrating from Microsoft SQL Server, Varchar(MAX) is now imported as LONGTEXT, instead of the erroneous VARCHAR(-1). (Bug #18105486, Bug #71253)
  • Altering a table's comment would immediately move the cursor position to the end of the comment. A workaround was to copy-n-paste a comment into this window. (Bug #17945616, Bug #70970)
  • MySQL Workbench failed to reverse engineer tables containing TIME(n) and DATETIME(n) (fractional timestamp) columns. (Bug #17559837, Bug #70515)
  • Executing Execute Now for a defined backup job would finish successfully, but would also report an error. (Bug #17408250)
  • When multiple versions of MySQL Enterprise Backup were installed, the MySQL Backup Command Path would include both paths. Now, the first discovered path is used, and a warning about having multiple MySQL Enterprise Backup installations is logged. (Bug #17367584)
  • The MySQL keywords were sometimes blank (missing) in the SQL Additions panel. (Bug #17346343, Bug #70116)
  • The Migration Wizard Overview text was updated to reflect better grammar. (Bug #17283213)
  • When too many tabs are present in MySQL Workbench, a double arrow now appears in the right top corner. When clicked, a list of the hidden tabs will appear. (Bug #16757127, Bug #69091)
  • The MySQL Workbench Scripting Shell did not allow tabs or spaces for indentation in interactive Python scripts. A workaround was to instead create and execute script files. (Bug #14520728, Bug #66451)
  • Sometimes the Report Bug window would remain open, even after pressing Cancel. (Bug #14495624, Bug #66084)
  • The panel dimensions for an EER diagram are now preserved. This left panel stores the descriptions, properties, and history tabs. (Bug #13972049, Bug #64661)
  • The Synchronize Model routine would only notice changes to some triggers, while ignoring changes to others. It would not update these triggers even if forced by using the Update Source button. (Bug #11766750, Bug #59934)
  • MySQL Workbench would allow a table group to be renamed using a reserved MySQL keyword. (Bug #11763690, Bug #56431)

New in MySQL Workbench 6.1.2 Beta (Mar 6, 2014)

  • 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 #71457)
  • A MEB backup could not be scheduled for December 31. (Bug #18019619)
  • 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 #17667094)
  • 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 #62464)
  • 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 #50251)
  • Relationship lines now snap to the closest snap point, rather than the most recently passed-over snap point. (Bug #11755408, Bug #47178)

New in MySQL Workbench 6.0.9 (Feb 6, 2014)

  • Functionality Added or Changed:
  • The restore operation can restore to a different schema. (Bug #11759068, Bug #51351)
  • Bugs Fixed:
  • MySQL Workbench now builds on Debian 7.0-unstable. (Bug #18041235, Bug #71156)
  • Ubuntu 13.10 is now supported. (Bug #18042416, Bug #71281)
  • On Linux, the Cancel button was written as "Cance" on some systems, depending on the GTK theme used on the system. (Bug #18042862, Bug #71106)
  • Sometimes, when exporting an EER diagram to SQL, the generated SQL code did not include "DROP SCHEMA" statements even with the Generate DROP SCHEMA option checked. (Bug #18054932, Bug #71243)
  • One tab could execute the query from a different tab, after swapping tabs. (Bug #17903147, Bug #71029)
  • On Linux, building MySQL Workbench from source would generate many glib related warnings with newer versions of glib. (Bug #17813170, Bug #70932)
  • After creating a new view inside a model, clicking Add View would display a new view in the editor this new could not be saved. (Bug #17796027, Bug #70904)
  • The --routines command line option was missing from the generated mysqldump command when multiple schemas were selected for a dump into a single file backup when the routines option was enabled. This could happen after executing the dump multiple times. (Bug #17795551, Bug #70896)
  • Executing Model, Forward Engineering with the Do not create users, only export privileges option enabled would recreate the user instead of simply changing privileges for the existing user. (Bug #17794653, Bug #70903)
  • On Linux, renaming foreign keys and indexes would crash MySQL Workbench. (Bug #17841664, Bug #70977)
  • On Mac OS X, switching colors with layers and tables several times could eventually cause a crash. (Bug #17758312, Bug #70841)
  • Adding a new table to an empty EER diagram would crash MySQL Workbench. (Bug #17775383, Bug #70872)
  • When building from source and without building the documentation, the documentation link will open the online MySQL Workbench manual. (Bug #17788936, Bug #70873)
  • The Inserts tab under Forward Engineering would sometimes unexpectedly fail. (Bug #17698069, Bug #70747)
  • The ENUM type now corresponds better to its definition better under Model, User Defined Types, to allow arguments. (Bug #17633506, Bug #70671)
  • On Microsoft Windows and Mac OS X, the bundled PyCrypto library was upgraded to version 2.6.1. (Bug #17615430)
  • MySQL Workbench could crash when using a MySQL connection that connects via an SSH tunnel with success, but is defined using incorrect MySQL server credentials. A dialog now requests the correct information. (Bug #17456433, Bug #70332)
  • The catalog treeview for an EER diagram was replaced by a central control with improved handling, which allows MySQL Workbench to worth more smoothly with a large number of tables. (Bug #17370413, Bug #69692)
  • Indexes that were auto-created for a Foreign Key can now be deleted in case another suitable index was available. (Bug #17275827, Bug #69937)
  • Under certain scenarios, the File, Print to File... action would not allow models to be unchecked. (Bug #17300434)
  • Model synchronization would complete, but if repeated then MySQL Workbench would ask to update the database again. (Bug #17033354, Bug #69591)
  • Changing the collation type would not always be detected, as "No changes detected" would be reported after attempting to apply the change. (Bug #16492371, Bug #68672)
  • The MySQL Forums link on the MySQL Workbench home page was updated, and it now links to a MySQL Workbench page that also links to the MySQL Workbench - Database Migration forum, when before it was difficult to find. (Bug #14773380, Bug #67272)
  • From Database, Reverse Engineer, and after selecting a schema with multiple tables, clicking the left or right arrow buttons with the Show Filter feature to include/exclude tables would lose the cursor position, and always move the cursor to the top of the list. (Bug #14017237, Bug #65018)
  • For models, tables can now be renamed by double-clicking the name column, and the columns edited. (Bug #13702831, Bug #64134)
  • A large SQL script file could not be saved for a model, although a limit of around 200MB limit still exists. (Bug #13025333)
  • MySQL Workbench could crash after choosing Recover when prompted to recover a model file from a previous session after MySQL Workbench was not closed properly. (Bug #13051204, Bug #62589)
  • Applying an large SQL Script object to a model could crash MySQL Workbench. (Bug #13025299)
  • The "Scratch" SQL editor tabs were removed, and instead standard SQL editor tabs are always opened. (Bug #11765876, Bug #58882)
  • Editing a mandatory relationship now updates the referenced column. (Bug #11764011, Bug #56792)
  • The Copy and Paste keyboard shortcut did not always function from within table cells in all environments. (Bug #11755245, Bug #46994)
  • The Schema Privileges tab was hidden in the Schema editor, and is now more viewable. (Bug #11758814, Bug #51066)

New in MySQL Workbench 6.0.8 (Nov 8, 2013)

  • Functionality Added or Changed:
  • A new MySQL Workbench preference (Preferences, SQL Editor) was added that sets the default comment type that is generated in the SQL Editor when clicking the "add comment" key combination. It can be either "--" (default) or "#". (Bug #16679373, Bug #68708)
  • Bugs Fixed:
  • When creating a table on a model diagram, an unhandled NULL reference exception was thrown when a second layer was drawn under some tables. (Bug #17561185, Bug #70518)
  • Restoring an incremental backup from a remote MySQL server would emit an unexpected error that referred to the WbAdminControl object. (Bug #17516320)
  • The Forward Engineer - SQL Create Script wizard would generate the LOCK TABLES privilege at the table level, instead of the database level. (Bug #17468314, Bug #70310)
  • On Microsoft Windows, after executing Search Table Data and viewing the results, right-clicking on a row and choosing Copy Query for Matches from the context menu would crash MySQL Workbench. (Bug #17506404, Bug #70411)
  • On Microsoft Windows 7, under some circumstances MySQL Workbench would not connect to a MySQL server on a RHEL 5 host. (Bug #17516617)
  • With Use most recent backup checked, an incremental backup made after another incremental backup would not be restored if the previous incremental backup failed. (Bug #17509626)
  • In the data result grid, selecting multiple fields and choosing Set Field(s) not Null from the context-menu would not alter the data. (Bug #17495179, Bug #70381)
  • When forward engineering an SQL CREATE script, checking the Omit Schema Qualifier preference would correctly remove the schema name from the CREATE statements, but it incorrectly left the schema name on the GRANT statements.
  • Command sequence: File, Export, Forward engineer SQL CREATE script. (Bug #17516695, Bug #70438)
  • On Microsoft Windows, having an empty SQL file saved in the AppData path would cause MySQL Workbench to not start.
  • A workaround was to delete the empty SQL file before starting MySQL Workbench. (Bug #17512088, Bug #70262)
  • On Linux, the Action Output would not auto scroll to place the latest action (executed SQL statement) in view. (Bug #17512005, Bug #70421)
  • An empty SQL script file could not be saved from within MySQL Workbench, and attempting this action would generate an unexpected error. (Bug #17468833, Bug #70365)
  • Executing Forward Engineer the Model to the local DB would generate an unexpected error. (Bug #17496362)
  • An unhandled exception would be thrown if the audit.log file was missing. (Bug #17452099, Bug #70323)
  • Data Import/Export for self-contained data will now only select *.sql files by default, and if an extension is not defined during an export, the extension will be set to .sql. (Bug #17449969, Bug #69069)
  • On Mac OS X, opening a new model and pressing the "Add EER Diagram" button from the toolbar would crash MySQL Workbench.
  • A workaround was to click "Add EER Diagram" from the navigation or context menus. (Bug #17437387, Bug #70284)
  • On Microsoft Windows, the mouse pointer inside a SQL Editor tab would rapidly change from pointer to cursor when the mouse was moved, thus creating a repeatedly flashing event. (Bug #17347406, Bug #70119)
  • Clicking Online Backup after deleting the configured MySQL Enterprise Backup directory (such as C:\MySQLBackupHome) would throw an unhandled exception.
  • Validation was added, a profile status icon was added to the backup screen, and MySQL Workbench now redirects to the Settings page instead of emitting an error. (Bug #17375285)
  • Double-clicking on an Audit Log File row would generate an unexpected error. (Bug #17376494)
  • While migrating a Microsoft SQL Server database to MySQL, database names with periods would fail, and now the periods are replaced with underscores. For example, "foo.bar" will become "foo_bar". (Bug #17370098, Bug #70170)
  • After selecting a table in the Catalog tab of the Catalog Tree pane, choosing Insert new row from the Edit Table... context menu would emit an unexpected error. (Bug #17357020, Bug #70140)
  • After editing a trigger in the model tab, switching tabs (such as loading a connection or SQL editor tab) would cause the new trigger edits to disappear. (Bug #17348212, Bug #70122)
  • Open query tabs were not persistent (reopened) after reopening MySQL Workbench. (Bug #17341182, Bug #17456474, Bug #17314977, Bug #70107, Bug #70325, Bug #70035)
  • Viewing the Client Connection could generate an unhandled exception if a connection had a very large connection time. (Bug #17375435, Bug #70174)
  • On Mac OS X, clicking Get Timestamp Ranges after selecting the available current filename from the Audit Plugin would throw an unhandled exception. (Bug #17300059)
  • The EER Diagram did not support some Chinese characters. (Bug #17275879, Bug #69933)
  • Having a !include in the MySQL configuration file would cause MySQL Workbench to crash at startup. (Bug #17271775)
  • Stored routine groups could not be updated via the group editor in the EER diagram.
  • A workaround is to use individual routine group editors for each routine, by dragging the routine objects into the members list of the routine group editor to group them. (Bug #17323855, Bug #70059)
  • I/O writes were reduced, which was especially a problem visible when closing MySQL Workbench with tables that had over 500 columns. (Bug #17283888, Bug #68276)
  • On Mac OS X, the full field names in the Performance tab of the Option Files navigator page would not be fully visible. (Bug #17323870, Bug #70057)
  • The Run, Script File sequence did not function. (Bug #17299680)
  • In the commercial edition of MySQL Workbench, the "MySQL Utilities" download button linked to the community version of MySQL utilities. It now links to the appropriate edition. (Bug #17316512, Bug #70049)
  • The Close Other Tabs context-menu option did not close Table Editor tabs. (Bug #17235359, Bug #69850)
  • The innodb_buffer_pool_size and innodb_buffer_pool_instances configuration parameters were duplicated in the Options File (formerly the Server Administration) tab. They were listed in both the Buffer Pool and Memory" groups.
  • Also, using MySQL Workbench to change these settings would generate a change that also altered whitespace in the MySQL configuration file. (Bug #16915510, Bug #69406)
  • Migrating a Microsoft Access database would crash at the Reverse Engineer Selected Schemata step. MySQL Workbench does not support the migration of Microsoft Access, so the migration wizard will now display an error (and halt operation) when attempting to migrate an unsupported database. (Bug #16529142, Bug #67584)
  • After adjusting the width of the Id or Time columns in the connection listing, the integer value was cut off without indication. The value is now shown, or an ellipses (...) is appended. (Bug #16464457, Bug #68593)
  • The Workbench Bug Reporter failed to log in to report a bug, even when using valid credentials. This bug reporting functionality was removed from MySQL Workbench. (Bug #16056820, Bug #14520752, Bug #67990, Bug #66343)
  • On Linux, WM_WINDOW_ROLE property is now properly set for all MySQL Workbench windows. (Bug #14171771, Bug #65537)
  • The Check for Updates, Submit a Bug Report, and Discuss a Topic MySQL Workbench buttons are now underlined when the mouse cursor hovers over them. (Bug #11758492, Bug #50704)

New in MySQL Workbench 6.0.6 (Aug 13, 2013)

  • Bugs Fixed:
  • On Microsoft Windows, MySQL Workbench would only detect the connection settings when the list of locally installed instances was detected. It now also detects the instance settings, such as the service name and configuration file location.
  • On Microsoft Windows, the Print to File feature could generate a corrupted PDF file.
  • Reading a my.ini file that contained a non-commented line before the first [section] would cause a crash.

New in MySQL Workbench 6.0.5 RC (Aug 2, 2013)

  • Bugs Fixed:
  • The mysql-workbench-gpl packages were renamed to mysql-workbench-community, and various RPM packaging fixes were made.
  • When performing a Sybase ASE migration, the custom length for TEXT, UNITEXT, and IMAGE columns was fixed as they do not allow a custom length.
  • MySQL Workbench would crash after excessive Control + C and Control + V operations on modeling objects.

New in MySQL Workbench 6.0.4 Beta (Jul 25, 2013)

  • Functionality Added or Changed:
  • MySQL Workbench will now detect file edit changes in the SQL editor. For example, you may now open an SQL file in MySQL Workbench, edit the same file in another text editor, and MySQL Workbench will detect the changes and update accordingly. (Bug #16744919, Bug #68950)
  • The tab navigation feature now includes wrapping. Pressing Control + Tab (forward) with the last tab active will move to the first tab, and pressing Control + Shift + Tab (backward) with the first tab active will move to the last tab. (Bug #14096668, Bug #65354)
  • A page header and footer was added to the Print to File... output.
  • A workaround option was to add a text field to the document and add your information there. (Bug #11762619, Bug #55233)
  • Bugs Fixed:
  • In the Model view, the "Accordion" style tabs would disallow scrolling when multiple tabs were open. For example, Physical Schemas would not scroll down to other options like Model Notes. (Bug #17154650, Bug #69635)
  • It was not possible to execute statements with the PROCEDURE ANALYSE statement.
  • A workaround was to remove the generated LIMIT clause. (Bug #17066330, Bug #69687)
  • A new preference was added to toggle casing for the generated keywords in the auto completion list. Edit, Preferences, SQL Editor TAB, Use uppercase keyboards on completion. (Bug #17033597, Bug #69621)
  • On Microsoft Windows, executing a query using the Control + Enter shortcut would cause the cursor focus to be lost. (Bug #16983168, Bug #69505)
  • Clicking "Alter Table" from the schema tables list and changing the engine from the engine drop down would not alter the database after pressing Apply. (Bug #16933119, Bug #69433)
  • The tables drop down was not sorted alphabetically in the schema explorer if a SELECT query was executed on a schema before viewing the tables. (Bug #16784484, Bug #69178)
  • Control + PageDown and Control + PageUp now switch between open SQL Editor connections. (Bug #16687676, Bug #68968)
  • The File/Open SQL Script dialog now defaults to the last used folder during the session. (Bug #16581302, Bug #68822)
  • The Revert option not working for views/routines. (Bug #16284542)
  • The Refresh data from data source option would fail to function with local changes present. A dialog was added to either apply or cancel the local changes before performing the refresh. (Bug #16104127, Bug #68030)
  • The Filter field in the query tab would ignore the last character. (Bug #14636440, Bug #66844)
  • A Rename Diagram... context menu item was added for diagrams in the Model Overview. (Bug #11762737, Bug #55367)

New in MySQL Workbench 6.0.3 Beta (Jul 10, 2013)

  • Functionality Added or Changed:
  • On Mac OS X 10.7 and above, full screen support was added. (Bug #16962994, Bug #69473)
  • Bugs Fixed:
  • The ";" separator for passing in multiple values to the replicate-wild-ignore-table option was not parsed correctly, and MySQL Workbench would throw an unhandled exception. (Bug #16996665, Bug #69520)
  • When executing an Administration task, such as Manage Security, an "Current Profile Has no WMI enabled" error would be reported for local connections.
  • A workaround was to edit and save the connection, while making edits to the connection was not required. (Bug #16986040, Bug #59933)
  • MySQL Workbench prompted for the sudo password when it was not needed. (Bug #16967758, Bug #69481)
  • Executing Synchronize Model against two tables that were identical except for the order that the indexes were created, would cause MySQL Workbench to drop and immediately re-add the foreign keys. (Bug #16999452, Bug #69153, Bug #69181)
  • Attempting to change my.cnf via Server Administration, Option File would generate an error about an invalid sudo password. (Bug #16941451)
  • On Mac OS X, the default configuration files for local server instances were not discovered properly. Attempts to edit the Options File would emit an error. (Bug #16977187, Bug #69475)
  • The checkbox in the bottom left corner of the Model, Model Options dialog box was not labeled. The label is now Use defaults from global settings. (Bug #17004380, Bug #69552)
  • On Microsoft Windows 8, a "Handle is not Initialized" exception would be generated after performing a "Find and Replace" in the routine tab that is located in the group routines section. (Bug #16892512, Bug #69354)
  • Adding a particularly long string (around 50 characters) to a table comment for a model diagram would cause MySQL Workbench to crash. (Bug #16703832, Bug #68984)
  • Creating a stored function or procedure would generate SQL with superfluous CREATE and USE statements. (Bug #16588163, Bug #68204)
  • Executing Model, DBDoc, Model Reporting created a memory link. Then after the report was generated, executing File, Export, Export as PNG would fail and report that MySQL Workbench ran out of memory. (Bug #16562737, Bug #68755)
  • Changing a column's default value from CURRENT_TIMESTAMP to CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP was not detected. (Bug #16546597, Bug #68341)
  • Clicking Apply after only changing a backtick ("`") or space (" ") would not save the results, and instead MySQL Workbench would report "No changes detected." (Bug #16545503, Bug #68162)
  • When connected to a database in SQL Development mode after running a query (or using the Edit table data context menu option), left clicking the leftmost column in the result set pane did nothing. The row options are now enabled when clicking the left side column. (Bug #16469383, Bug #68633)
  • After creating a table against a MySQL server with lower_case_table_names enabled, the Object Browser would display the new table name as the user entered it, instead of displaying how it was created with lower-case. The lowercase version is now displayed, and the user is notified of the conversion. (Bug #16390426, Bug #68210)
  • The Replace & Find feature would insert the replacement text at the cursor location even if the matching text was not found. (Bug #16284625)
  • On Microsoft Windows, an "Index was out of range" exception was thrown after loading the Output tab in the SQL editor. (Bug #16283047)
  • The text editor in the lower bottom half of the snippets tab (inside the scripting shell) would become unavailable (hidden) after dragging the splitter bar all the way down. (Bug #16277909)
  • The **.* object under Model, Schema Privileges, Privileges was missing an icon. (Bug #16285241)
  • An error was emitted while generating a catalog diff report, and differences in catalogs are now successfully reported. (Bug #14692908, Bug #66986)
  • The canvas height of the Model Overview container was not calculated properly. The amount of whitespace would increase as the number of objects increased. (Bug #14456267)
  • Right-clicking on an existing diagram in the model editor would display a disabled Cut and Paste option. It was removed. (Bug #13470625)
  • An error dialog is now generated if an invalid column is chosen from the foreign key picker when creating the relationship. (Bug #11766525, Bug #59655)
  • When adding a table to form a N:M relationship in a large EER Diagram, the new N:M table was positioned far away from the tables. This third table is now added between the two other tables. (Bug #11754898, Bug #46582)
  • The name of a Diagram can now be changed from the diagram tab via Model, Diagram Properties and Size.... (Bug #11753099, Bug #44472)

New in MySQL Workbench 6.0.2 Beta (Jun 14, 2013)

  • Functionality Added or Changed:
  • A new Hide sleeping connections option was added to the Client Connections section of the MySQL MANAGEMENT tab. (Bug #16675975, Bug #68978)
  • The Select All and Unselect All (database) commands were added to the Synchronize Model context menu. (Bug #14084381)
  • Table column and relationship defaults may now be configured to default as lowercase, uppercase, or capitalized (for camelCase). The syntax, under Preferences, Model is %table|upper%, %table|lower%, and %table|capitalize%. See the hovering help tool tips for additional information. (Bug #11753021, Bug #44382)
  • A Truncate Table option was added to the right-click context menu for tables, which compliments the current Alter Table and Delete Table options. (Bug #11758513, Bug #50726)
  • Relationship properties can now be edited by double-clicking the relationship in an EER diagram. (Bug #11758318, Bug #50506)
  • Bugs Fixed:
  • Specifying an ip/subnetmask as a host specification would be rejected. For example, "10.0.1.0/255.255.254.0" would fail to validate as a host. (Bug #16887657)
  • Right clicking a field in the SQL Editor while in grid view would cause MySQL Workbench to freeze. (Bug #16762969, Bug #69139)
  • Executing a query that contained a regular expression would cause MySQL Workbench to crash. (Bug #16775867, Bug #69167)
  • An older version of the MySQL Client was bundled with MySQL Workbench, and it has since been updated. This caused problems while executing mysqldump. (Bug #16575396, Bug #16668532, Bug #16307109, Bug #68683, Bug #68779, Bug #68328)
  • On Microsoft Windows, migrating an SQL Server database that contained a lot of columns (100+) would sometimes fail to migrate. The problem involved how wbcopytables.exe uses temporary files to store table names and column information. (Bug #16538786, Bug #68146)
  • Upon synchronization between a model and a database, the database SQL code is no longer displayed when changes are applied to a model or set as ignored. (Bug #16529438, Bug #67692)
  • Statements following a "--" style code comment would not be executed. These comments are now handled properly by MySQL Workbench. (Bug #16492436, Bug #16171620, Bug #15978566, Bug #68674, Bug #67711, Bug #67848)
  • On Microsoft Windows, scripts generated for wbcopytables.exe would not escape parameter values that contained spaces or semi-colons. (Bug #16463467)
  • When configured to generate a script for data copying on the Data Transfer Setup page in the Database Migration wizard, the Truncate target tables... and the Enable debug output... options were not generating commands for this script. (Bug #16464193)
  • While copying tables, the Database Migration wizard would create temporary files in the current directory upon execution. This would sometimes lead to permission errors, so the system's temporary folder is now used. (Bug #16447313)
  • The Manual Editing step of a Database Migration would display all columns, but will now only show the columns that were selected for migration. (Bug #16446660)
  • Executing a very large statement could produce generic GDI+ errors, and replace the process list with a large red X. (Bug #16453590)
  • Using Synchronize with Any source would not display all available schemas for the source connection. (Bug #16471554, Bug #67887)
  • Edit Table Data was removed from the table context menu, and the table name was added as the title for the Select Rows - Limit 1000 context menu option that can be used to edit table data. (Bug #16346058, Bug #68398)
  • The Server Administration, Configuration, Options File editor would sometimes fail to display the options. (Bug #16346058, Bug #68398)
  • When synchronizing a model with columns with default values of NULL, MySQL Workbench would always treat these columns as having changed. (Bug #16325636, Bug #68369)
  • Adding a new connection using the Manage Stored Connection option in the Synchronize Model dialog would not save the connection after MySQL Workbench was closed. (Bug #16292166, Bug #68294)
  • Selecting and then dropping multiple objects from the SQL editor would cause MySQL Workbench to delete the objects, and then crash. (Bug #16311466, Bug #68337)
  • Comments added to primary keys were not saved. (Bug #16329439)
  • A database with a name that contained an underscore could not be assigned schema privileges using the provided database list in the Server Administrator, as the database name was not escaped properly. (Bug #16227715, Bug #68175)
  • Datetime with fractional seconds is now supported. Before, MySQL Workbench would convert DATETIME(n) (where "n" is an integer) to DATETIME. This fix also applies to TIMESTAMP(n).
  • Note that this option requires the default target MySQL Server version set to "5.6", which is set with the Model, Model Options preference. (Bug #16239203, Bug #68191)
  • The -upgrade-mysql-dbs command line option was missing from -help. (Bug #16278270)
  • Clicking Cancel after loading Plugins, Utilities, Change the Storage Engine of All Tables would generate an error. (Bug #16248101, Bug #68232)
  • Default values for DECIMAL column definitions would not be preserved during synchronization. (Bug #16171808, Bug #67502)
  • Running Database, Reverse Engineer on an EER Model diagram would cause the canvas to not draw properly until the diagram was dragged. (Bug #16171635, Bug #67440)
  • While editing a schema comment, the cursor would jump to the end of the comment after the cursor was moved, thus making it impossible to edit previous comments. (Bug #16104719, Bug #67843)
  • Opening a stored procedure or function for editing in a Model, editing it, and then closing the tab, would crash MySQL Workbench. (Bug #16058044, Bug #67995)
  • The Action Output window would not refresh when the Text Output window was not active. (Bug #16063275, Bug #67419)
  • A Database Migration from SQL Server to MySQL could fail if a SQL Server data type was a FLOAT(n). (Bug #14761954, Bug #67234)
  • MySQL Workbench could crash after modifying a functioning SSH key-based authenticated stored connection with incorrect credentials. (Bug #14701987, Bug #65672)
  • When migration SQL Server to MySQL, CHAR/VARCHAR/TEXT fields containing international text would fail to transfer. These fields are now converted to NCHAR/NVARCHAR/NTEXT. (Bug #14534789, Bug #66516)
  • Clicking Cancel after loading Alter Table, Partition would duplicate the partition on the screen once for every time Cancel was clicked. (Bug #14571162, Bug #66615)
  • MySQL Workbench will now check if collation and charset are compatible, and in the case of generated SQL, the charset will be ignored if they are incompatible. (Bug #14278043, Bug #65764)
  • A connection could fail to connect prematurely and would report "Connection canceled" despite Test Connection reporting a valid connection. (Bug #13972036, Bug #64003)
  • A trigger meant to insert connections on an n-n relationship would fail on INSERT due to a wrong insert order produced during the Forward Engineering step.
  • A workaround was to forward engineer the database with the Skip Foreign Key creation and Skip FK Indexes options enabled while executing Synchronize Model. (Bug #13790046, Bug #61594)
  • The Alter Table... option did not function on tables with triggers. This was resolved by correctly escaping the data returned by the MySQL Server when retrieving the triggers. (Bug #12546727, Bug #61110)
  • The image data viewer tab in the BLOB image viewer would not have a horizontal tab when the image was larger than the image viewing area. (Bug #11764016, Bug #56797)
  • Deselected table objects were still evaluated when executing the EER Model From Existing Database wizard on a database with triggers. (Bug #11765398, Bug #58362)
  • Window placement improvements were made for using MySQL Workbench with lower screen resolutions than the minimum screen resolution requirement of 1024x768. (Bug #11764019, Bug #56802)
  • When Synchronize Model the feature was used to generate SQL to modify an existing database, it would lose the UNSIGNED attribute while executing the synchronization. (Bug #11760008, Bug #52373)
  • It was not possible to force synchronization of a schema with another schema that had a different name. The new Override Target option allows this, and is available during the Select Schemata stage of the synchronization wizard.
  • Note: you must click Override Target to set the override before clicking Continue. (Bug #11754001, Bug #45533)
  • The length of a primary key index could not be set when the primary key contained a text field. (Bug #11763301, Bug #55997)
  • Clicking on a table cell and pressing F2 will now select (highlight) the cell contents for editing. Before, the cursor would be placed at the end of the cell. (Bug #11759671, Bug #52001)

New in MySQL Workbench 5.2.46 (Feb 5, 2013)

  • Functionality Added or Changed:
  • New role functionality was added. It is now is possible to add schemas.*, tables.*, and *.*, and to assign privileges to each object. Before it was only possible to add individual tables when defining roles. (Bug #11761640, Bug #54153)
  • The auto-completion feature was improved. For example, it now includes the parsing of aliases and subqueries for SELECT statements.
  • Bugs Fixed:
  • Microsoft Windows: In an EER Diagram, the circles at each end of a relationship line were rendered as different sizes. (Bug #12628088, Bug #54663)
  • Refreshing data in the Server Administration panel would reset the sort order, and the sorting order would default back to Connection ID. This could also cause the sorting method to be mislabeled. (Bug #16206194)
  • Closing a table's properties window from within the EER Model diagram window would crash MySQL Workbench. (Bug #16185134, Bug #68101)
  • An SQL syntax error would be reported when a comment was added to an INDEX. (Bug #15991038, Bug #67835)
  • Two preference settings were added for online DDL operations. Listed under Preferences, SQL Queries, under Online DDL, these new settings (Default algorithm for ALTER table and Default lock for ALTER table) set the default values for the Apply Script wizard, or these values may be defined when Apply Script is executed. (Bug #15893626)
  • Functionality (such as Copy to Clipboard) was missing from the right-click context-menu of the Schema browser when multiple columns were selected. (Bug #14834245, Bug #67417)
  • The Show Filter table listing for Export MySQL Table Objects is now sorted alphabetically. (Bug #14706782, Bug #66712)
  • From the EER Diagram window, nearly completing the Database, Synchronize with Any Source wizard, and then pressing Back to the beginning, MySQL Workbench would crash after nearly completing the wizard the second time. (Bug #14611078)
  • The Bulk Data Transfer migration step would fail if too many tables were being migrated, because too many arguments were being passed to the command-line. This table listing is now saved to a new file named wb_tables_to_migrate.txt, which is now read during the migration process. (Bug #14588167, Bug #66611)
  • MySQL Workbench could crash (segmentation fault) at startup if a configuration file was corrupt. (Bug #14622471, Bug #66776)
  • Creating a table in a schema that had a "-" in the schema name would emit an error about an "unknown column", and fail to create the table. (Bug #14632271, Bug #66815)
  • MySQL Workbench could crash after files became corrupted, but now attempts to regenerate the corrupted files. (Bug #14520133, Bug #65630)
  • Sometimes the Create Table... dialog in the Object Browser would emit an error instead of creating the table, after pressing Apply. (Bug #14520406, Bug #66169)
  • On Linux, the right-click context menu would differentiate between unselected and selected rows, when called from within the SQL editor results view panel. This menu is now consistent. (Bug #14539036, Bug #66308)
  • Changes to a table that a view referenced would cause an error while attempting to edit the view. This fix allows MySQL Workbench to work around the underlying bug, which is MySQL bug #61718. (Bug #14526308, Bug #66502)
  • The ability to select code in the SQL Editor by clicking on line numbers was restored. (Bug #14483713, Bug #66139)
  • On Mac OS X, and in the table editor, the schema name was changed from a dropdown-box to a simple label. (Bug #14456213)
  • Right-clicking on a tab name did not show the New Tab, Save tab, Close other tabs, and Copy path to clipboard options. (Bug #14171956, Bug #65455)
  • Selecting the server engine default within the Alter Table window would generate an error. (Bug #14076198, Bug #65101)
  • On Linux, the Edit, Preferences menu did not wrap properly, and was too narrow so it would hide (cut) text. (Bug #14070969, Bug #64917)
  • The Model: MySQL, Default Storage Engine preference would not take effect until after MySQL Workbench was restarted. (Bug #13970619, Bug #64928)
  • On Microsoft Windows, holding down Shift with the Spacebar would not enter a space. (Bug #13919870, Bug #64820)
  • Changes to File, Document Properties for a Model were not detected or saved by MySQL Workbench. A Save prompt is now generated. (Bug #13040173)
  • MySQL Workbench would hang when attempting to connect with user accounts that utilized external authentication. (Bug #12896935)
  • On Linux, clicking Apply Changes when the cursor focus was in a data cell, the data content was not saved. (Bug #12922070, Bug #62232)
  • The EER diagram Arrange, Center Diagram Content option would hide objects from the diagram. (Bug #12898144)
  • If MySQL Workbench crashed when an EER diagram was being created, after restarting MySQL Workbench the EER diagram would be listed as "unsaved" but would not open. And it could not be deleted from the diagram list. (Bug #12642422, Bug #61444)
  • After selecting multiple objects and choosing delete, then choosing keep when prompted to delete or keep the selected objects, the relationship lines were still deleted. MySQL Workbench now asks if the relationship columns should be deleted or kept. (Bug #12565850, Bug #61113)
  • Under certain circumstances, synchronizing a database to a model would remove the mandatory relationships. (Bug #11834230, Bug #60312)
  • Changes made to a database schema while the Database, Synchronize Model wizard was active, would throw an exception. (Bug #11765036, Bug #57948)
  • On Linux, a warning will now warn you after attempting to close the SQL Editor when unsaved INSERT changes still exist.
  • Also, all platforms (Linux, Mac OS X, Windows) are now consistent, and will also warn you after attempting to close MySQL Workbench with any unsaved changes. (Bug #11758193, Bug #50363)
  • The Default Schema setting was ignored by the Reverse Engineer Database wizard. (Bug #11757887, Bug #50002)
  • The bundled MySQL Client was updated to version 5.6.10.

New in MySQL Workbench 5.2.45 (Dec 28, 2012)

  • Functionality Added or Changed:
  • Models: Copy, Cut, and Paste options were added to the context menu (right-click) of the Columns list in the models table editor. These options can be used between models. (Bug #13029519, Bug #62503)
  • A Copy Selected button was added to the Server Status panel of the Server Administration window. It copies the query of the selected connection to the clipboard. (Bug #14799336, Bug #66728)
  • The Control + / keyboard shortcut was added to comment/uncomment lines while editing SQL queries. (Bug #14803414, Bug #67002)
  • An Import Recordset from CSV File option was added to the SQL Editor and model insert tabs. This import functionality parses a file with comma-separated values. (Bug #14207773, Bug #65592)
  • Bugs Fixed:
  • Linux: Right-dragging saved connections, models, and MySQL Server instances on the home screen could crash MySQL Workbench. (Bug #14812457)
  • Linux: Executing MySQL Workbench from the command-line would print stdout twice. (Bug #14565095, Bug #66590)
  • Mac OS X: The results window from executing an SQL query could be empty. A workaround was to resize the results window. (Bug #14520361, Bug #66446)
  • Mac OS X: Closing MySQL Workbench after executing and making changes with the Alter Table tool would not prompt the user with the save dialog. (Bug #14456136)
  • Mac OS X: On Mac OS X, the default column name and column type model preferences did not function. Note that this feature does not function on Linux. (Bug #14399236, Bug #66090)
  • Mac OS X: The ability to select multiple columns in the models table editor did not function on Mac OS X. It is now possible to use Shift, Command, and mouse dragging. (Bug #11766291, Bug #59372)
  • Models: Microsoft Windows: After opening and then closing a model file from the file manager, attempts to open a different model file would fail to load the model. (Bug #14791573, Bug #67312)
  • Models: Microsoft Windows: Model files (*.mwb) would not load MySQL Workbench after being double-clicked in Windows Explorer. (Bug #14521111)
  • Microsoft Windows: Pressing Control + A in the table editor on a table field would select all table entities instead of the text in the field. (Bug #15884658, Bug #67610)
  • Microsoft Windows: Clicking on the Schema and Schema Objects column headers within Server Administration, Data Export would properly sort in descending order, but would not sort in ascending order when clicked again. (Bug #15849616, Bug #67518)
  • Microsoft Windows: The Enter key would not create newlines within the table column comment dialogue. (Bug #14829617, Bug #67320)
  • Microsoft Windows: Queries surrounded by parenthesis would not display results in the view tab. (Bug #14651969, Bug #66887)
  • Microsoft Windows: Right-clicking on a database name in the schema browser and choosing Set as Default Schema would add a strikethrough to the chosen database name. (Bug #14663690, Bug #66930)
  • Microsoft Windows: The Explain button would not display the results in the Explain tab. (Bug #14702591, Bug #67059)
  • Microsoft Windows: The Id and Time columns within the Server Administration, Server Status, Connections panel would not sort properly, as they were sorted as ASCII values instead of numerically. (Bug #14612413, Bug #66768)
  • Microsoft Windows: A model would fail to load when opened from the Microsoft Windows 7 taskbar if a different model was already open. (Bug #14621880, Bug #66799)
  • Microsoft Windows: Control + H did not invoke the replacement function. (Bug #14520920, Bug #66422)
  • Microsoft Windows: After using the schema search filter in the object browser, right-clicking on a filtered schema would generate a context menu with invalid options. (Bug #14521006, Bug #66346)
  • Microsoft Windows: Find and Replace would not function properly while using '_' as a replacement character. (Bug #14499088, Bug #66390)
  • Microsoft Windows: The Explain Current Statement option would not function. A workaround is to manually prepend EXPLAIN to your query. (Bug #14483518, Bug #66157)
  • Microsoft Windows: Control + A would not always select data from cells in the query results tab. (Bug #13891109, Bug #64723)
  • Microsoft Windows: The default plugin directory in the configuration tab was set as a Linux style path such as "/usr/", but it is now based on the OS aware BASEDIR value. (Bug #11764440, Bug #57271)
  • MySQL Server 5.6: The SHA-256 Authentication Plugin is now supported. (Bug #14786561, Bug #67155)
  • MySQL Server 5.6: MySQL Workbench would alter the mysql.* system tables for tasks such as account management, instead of using the corresponding account manipulation statements. This would conflict with GTID usage as of MySQL Server 5.6. (Bug #14786531, Bug #67150)
  • MySQL Server 5.6: The MySQL 5.6 ALTER USER ... PASSWORD EXPIRE option is now supported. An expired password indicator, and an Expire Password button to expire the current password, were added. (Bug #14786564, Bug #67157)
  • MySQL Server 5.6: MySQL Workbench now supports MySQL Server 5.6 configuration options. (Bug #14786556, Bug #67153)
  • MySQL Server 5.6: The SQL Editor would emit invalid syntax errors with MySQL 5.6 queries. For example, GET DIAGNOSTICS queries would return "syntax error, unexpected IDENT_QUOTED, expecting ':'". (Bug #14786599, Bug #14786604, Bug #14786615, Bug #67163, Bug #67164, Bug #67168)
  • MySQL Server 5.6: MySQL Workbench would not allow passwords to be created or changed for user accounts that utilize the SHA-256 Authentication Plugin, which exists as of MySQL Server 5.6.6. (Bug #14786567, Bug #14786558, Bug #67158, Bug #67154)
  • MySQL Server 5.6: The partition count definition was limited to 1-10 as a drop-down selector in MySQL Workbench. This option is now a text field, which accommodates the 8192 partition limit in MySQL Server 5.6. (Bug #14786614, Bug #67166)
  • MySQL Server 5.6: A DDL related parsing error would be generated while attempting to update an existing routine that contained a DateTime variable type with precision. This feature is specific to MySQL Server 5.6. (Bug #14684874, Bug #14545075)
  • MySQL Server 5.6: Creating a standard user with MySQL Server 5.6 would sometimes fail, and emit an error that referred to an unknown mysql_native_password plugin. (Bug #14574998, Bug #66638)
  • MySQL Server 5.6: The MySQL Workbench UI now supports the extended TIMESTAMP and DATETIME features that MySQL Server 5.6 offers. Both the initial and on-update values can now be defined for these types, and the fractional-second granularity is also now supported. (Bug #67165, Bug #67169, Bug #14786605, Bug #14786616)
  • MySQL Server 5.6: All MySQL Server 5.6 system variables were listed under the Other tab instead of their proper location. For example, gtid_done is now listed under the Replication tab. (Bug #67170, Bug #14786569)
  • MySQL Server 5.6: Creating a standard MySQL Server 5.6 user account in MySQL Workbench would fail, and emit an error related to the msyql_native_auth plugin. (Bug #67151, Bug #14786542)
  • MySQL Server 5.6: The creation of a username and password will now utilize the Password Validation Plugin in MySQL 5.6. This option is available within the Server Administration section, under the Security Options tab. (Bug #67152, Bug #67161, Bug #14786551, Bug #14786626)
  • Migration: Migrating a Microsoft SQL Server database would fail if nvarchar(max) was used. These are now converted to LONGTEXT. (Bug #14780416, Bug #67289)
  • Migration: From within the Manual Editing section of the database migration procedure, viewing Migration Problems after All Objects would continue to display information from All Objects. (Bug #14761792, Bug #67229)
  • Migration: Migrating from MySQL Server 5.0 to MySQL Server 5.6 could fail. The migration tool now supports MySQL Server 4.1 and above as the source database. MySQL Server 5.1 and above are supported as the target database. (Bug #14647426, Bug #66861)
  • Models: Switching from a table column tab to a different tab, and then back to the column tab, would add an empty column named "tablenamecol". This empty column would be added to the table unless Escape was pressed. (Bug #14768685, Bug #67235)
  • Models: Model notes could not be saved. The Apply Changes button is available again. (Bug #14813462, Bug #67211)
  • Models: Synchronizing a model with a database could crash MySQL Workbench by causing a segmentation fault. (Bug #14588524, Bug #66707)
  • Models: While executing the Synchronize Model with Database wizard, invalid trigger related errors could be emitted even though the definitions were correct. (Bug #14498358, Bug #65982)
  • Models: Forward Engineering a model with users and roles could generate invalid SQL, because the username was not escaped within the generated GRANT statements. (Bug #14396930, Bug #66070)
  • Models: The File, Import, Import DBDesigner4 Model feature would fail to function. (Bug #13548113, Bug #63878)
  • Models: Sometimes a modified stored procedure would not be flagged as modified while synchronizing a model. (Bug #13364922, Bug #62595)
  • Models: The ability to open model files from older versions of MySQL Workbench has been improved. (Bug #12747012, Bug #61703)
  • Models: Pressing Cancel in either the Create EER Model from Existing Database or Create EER Model from SQL Script dialogs would still open a Model tab. (Bug #11757140, Bug #49145)
  • Models: When editing an EER diagram, the Cut context menu option follows Delete behavior by also deleting the schema object. It will now only remove it from the EER canvas. And a new Remove option was added that also only removes an object from the EER canvas. (Bug #11761492, Bug #53994)
  • Saving script files did not function properly with the clipboard. Content pasted from the clipboard was not saved. (Bug #15837775, Bug #67462)
  • Clearing the output window while a query was running could cause MySQL Workbench to crash after the query finished. (Bug #15891884, Bug #67618)
  • Having sql_mode set to PAD_CHAR_TO_FULL_LENGTH causes the routine functionality to fail, as MySQL Workbench is not designed for this setting. A connection specific sql_mode option was added, and it can be set from the Advanced tab in the Connection Editor. It defaults to "". (Bug #14845656)
  • The following scenario would crash workbench: open a table, insert a new row of data, close the table, open a different table via double-click, then press Save Changes. (Bug #14829570, Bug #67237)
  • Added DbMySQLQuery->affectedRows, fixed MySQLResult->firstRow, and added a Splitter control to the Python binding for mforms. (Bug #14799403, Bug #66804)
  • MySQL Workbench would fail to interpret C-style comments, such as /*! MySQL-specific code */. For more information about comment usage in MySQL, see Comment Syntax. (Bug #14807602, Bug #67203)
  • Opening a connection using Open connection to Start Querying from the MySQL Workbench home screen could crash MySQL Workbench. (Bug #14803527, Bug #67074)
  • Procedures were always included in the exported SQL, even if excluded via a filter or configuration setting. (Bug #14758896, Bug #66790)
  • The Select Objects to Forward Engineer filter was ignored while executing Forward Engineer to Database. All tables were exported. (Bug #14696609, Bug #67031)
  • A model could not be synchronized if a field contained a comment with a single quote. (Bug #14582241, Bug #66680)
  • A crash could occur after switching tables in the EER Diagram tab while the Privileges was open, or while adding roles to the active table. (Bug #14645542, Bug #66869)
  • In the MySQL Workbench Scripting Shell, an exception is now thrown while attempting to use input() or read from stdin. (Bug #14520741, Bug #66452)
  • The non-functional comments box was removed from the schema editor. (Bug #14548126, Bug #66553)
  • An exception would be generated when executing Forward Engineer without a MySQL Server connection. (Bug #14574987, Bug #66648)
  • Lower level changes, such as a newly created TRIGGER, would not be visible after the object browser was refreshed. (Bug #14551801, Bug #66549)
  • The mouse scroll would not function while viewing the Options File in the Server Administration panel. (Bug #14388344)
  • Unlike the Server Administration panel (since 5.2.35), the SQL Editor did not support syntax that utilized the authentication plugins. (Bug #14356470)
  • The Server Access Management interface would not allow a password to be set as an empty string. (Bug #14278189, Bug #65739)
  • The Limit Connectivity to Hosts Matching option did not allow an IP with a Subnet Mask because "/" was considered an invalid character. (Bug #14207793, Bug #65583)
  • Having multiple connections with TCP/IP over SSH could cause MySQL Workbench to not connect when exceeding MaxAuthTries. This may happen if an encryption type is unknown. The bundled paramiko library (on Mac OS X, and Windows) was updated to version 1.7.7.1, which helps solve this problem, as it adds known support for OpenSSL keys. (Bug #13919914, Bug #64802)
  • Multiple instances of MySQL Workbench will no longer open the same database model file. Doing so caused problems with features such as auto save and file locking. (Bug #13864687, Bug #64639)
  • An SSL connection required a client certificate. (Bug #13851229, Bug #61266)
  • A new General, SQL Editor option was added. Enabling Create new tabs as Query tabs instead of File (disabled by default) causes new SQL Editor tabs to default as Query tabs instead of SQL File tabs. File tabs include additional options, and prompt to be saved when the tab closed. (Bug #13492434, Bug #14541178, Bug #62929, Bug #66541)
  • Changing a foreign key column to be nullable now deselects the mandatory checkbox. If all foreign key columns are set to NOT NULL, then the mandatory checkbox value will be selected. (Bug #13252655, Bug #62737)
  • The Start Command Line Client feature would fail to connect with SSH connections. (Bug #12612343, Bug #61325)
  • A Refresh Rate option was added to the Server Administration, Server Status window. The refresh rate defaults to "Don't Refresh" and includes options ranging from 0.5 to 30 seconds. (Bug #11926869, Bug #60546)
  • It was not possible to sort schemas for exporting. (Bug #11926862, Bug #60566)
  • Changes to the DEFINER clause were not detected by the Alter Table wizard when altering this clause was the only change. (Bug #11829867, Bug #60164)
  • When foreign keys are added, existing indexes are now used instead of always creating new indexes. (Bug #11760834, Bug #53277)
  • Attempting to open MySQL Doc Library while it was already opened would generate an error. (Bug #11763691, Bug #56432)
  • The ALTER ROUTINE functionality would not detect stored procedure changes when only the case changed. This check was case-insensitive. (Bug #65277, Bug #14136994)

New in MySQL Workbench 5.2.44 (Sep 29, 2012)

  • Functionality Added or Changed:
  • Updated the bundled MySQL Utilities to version 1.1.0, which includes the new mysqluc console.
  • Added native migration support for PostgreSQL and Sybase ASE.
  • Bugs Fixed:
  • After right-clicking on a non-empty field in the SQL editor, and choosing Copy Row Content, pasting the row into an empty row (by right-clicking and choosing Paste Row) would not increment the row id when it was appropriate to do so. (Bug #14587186, Bug #66668)
  • When a table from Microsoft SQL Server was migrated to MySQL, TEXT columns were mapped to VARCHAR(16). They are now mapped to LONGTEXT because Microsoft SQL Server TEXT columns have a maximum length of 2^31 - 1. (Bug #14556732, Bug #66584)
  • The MySQL Workbench Data Export feature would fail to recognize tables that contained accented characters in the table's name. (Bug #14504342, Bug #66421)
  • The object browser would not update the column order after a table was altered. (Bug #14495629, Bug #66232)
  • On Mac OS X systems with the Retina display, the mouse cursor would register incorrect mouse coordinates. (Bug #14396939, Bug #65607)
  • Entering the caret ("^") character inside the SQL editor, followed by any other character, could cause MySQL Workbench to hang. This was a Scintilla bug that is now fixed. (Bug #13930994, Bug #64848)
  • After choosing Alter Table, pressing Apply would cause MySQL Workbench to display "Preparing..." in the output panel, but it now displays "No changes detected." (Bug #13497239, Bug #63604)
  • When synchronizing a model to a database after changing a field definition from NOT NULL DEFAULT x to NULL DEFAULT NULL, the model synchronization would correctly generate the SQL. But after executing this SQL and resynchronizing, MySQL Workbench

New in MySQL Workbench 5.2.36 (Dec 5, 2011)

  • Functionality Added or Changed:
  • The Edit, Format, Beautify Query feature no longer quotes column names. (Bug #13030351)
  • The edit context menus, such as Edit Table Data, now open as new tabs. Before they reused (overwrote) the same tab. (Bug #61774, Bug #12731459)
  • If only one server instance is defined, then the Server administration, Manage security option will now automatically connect to it, instead of prompting to choose a server instance. (Bug #61451, Bug #12647697)
  • Indexes are now shown within the schema tree. And indexed columns are also indicated within the table information panel. (Bug #61295, Bug #12616367)
  • The auto_increment information is now displayed within the SQL editor. (Bug #60933, Bug #12402845)
  • On the SQL Editor tabs, right-clicking a tab now offers the following options: New Tab, Save Tab, Close Tab, Close Other Tabs, and Copy Path to Clipboard. (Bug #60883, Bug #12399369)
  • The query and associated results are no longer displayed in separate tabs, but they are now viewable within a single interface. (Bug #60624, Bug #11926853)
  • The SQL editor windows did not have maximize or minimize buttons, but these windows are now opened in configurable tabs. (Bug #60606, Bug #12617245)
  • The export result set dialog has been redesigned, and now saves the previously used settings. (Bug #60490, Bug #11889185)
  • SQL snippets can now be edited, and then saved. (Bug #58879, Bug #11765873)
  • Tab spacing is now defined as 4 on the Linux and Mac platforms, to be consistent with Windows. (Bug #58867, Bug #11765862)
  • A Paste Row context option was added to the Edit Table Data menu of the Object browser. (Bug #58169, Bug #11765228)
  • Additional Export data types were added to the SQL Browser, which now includes JSON, Excel spreadsheet, and MySQL formatted XML. (Bug #56808, Bug #11764024)
  • The Overview tab was replaced, in favor of the new schema tree view. (Bug #56795, Bug #11764014)
  • Added the ability to edit data from a result set after executing a query. If MySQL Workbench determines that a returned result cannot be edited, then a read-only icon will be displayed, and hovering over the icon reveals a tooltip that explains why it cannot be edited. (Bug #56794, Bug #11764013)
  • Added a input field to filter the schema list in the Object Browser. (Bug #55162, Bug #11762554)
  • The Alter table option defaulted to Table view, but now uses the new table editor. (Bug #55050, Bug #11762454)
  • MySQL Workbench did not support the .dbquery file extension. (Bug #54321, Bug #11761795)
  • Added the Copy Inserts to Clipboard option to the Plugins, Objects menu. (Bug #54036, Bug #11761531)
  • Added toolbar buttons to toggle the sidebars and bottom panel of the SQL Editor. (Bug #53714, Bug #11761243)
  • The table view within the Object Browser has changed. The table view includes another level of grouping, which includes Columns, Indexes, Foreign Keys, and Triggers. Before, only the columns were listed. (Bug #53504, Bug #11761050)
  • The table information window within the Object Browser has been expanded to include foreign keys, triggers, indexes, and data types. (Bug #53502, Bug #11761048)
  • The Overview tab was removed, in favor of the new schema layout. (Bug #53323, Bug #11760879)
  • New entries to the error log are now shown when restarting the MySQL server.
  • When log_output is set to FILE, the log files are now displayed in the MySQL Workbench log page. (Bug #52445, Bug #11760073)
  • The SQL snippets interface been redesigned and relocated to its own sidebar. Its display may also be toggled. (Bug #50069, Bug #11757950)
  • The SQL Editor history tab now auto-scrolls to the bottom, so that the most recent entry is visible. (Bug #49317, Bug #11757294)
  • Added a new format to the SQL Editor for export, which is identical to the XML generated by the mysql --xml command. It's titled XML (mysql format). (Bug #49305, Bug #11757284)
  • Added the ability to copy Status and System Variables to the clipboard. (Bug #49074, Bug #11757074)
  • Bugs Fixed:
  • While using the import/restore feature of the server instance administration area, views and routines were not imported. (Bug #13041684)
  • After right-clicking a cell within the insert grid of the model table editor, an unhandled exception was generated on Microsoft Windows, and a fatal error on Mac OS X. (Bug #13029647)
  • The Manage Security window initially shows the first connection as selected, but it is not. (Bug #13026478)
  • While administrating a server instance, importing a project folder will result in an "Import from Disk" error after the following sequence: Data Export and restore, Export to Dump project folder, with Dump views and Dump stored routines... checked, then exporting a schema with views and/or routines, opening the SQL Editor and dropping the exported schema, then clicking Import to Disk within the server administrator. (Bug #13025419)
  • Pressing Refresh within the Slow Query Log tab resulted in an unhandled exception. (Bug #12928308)
  • Within a diagram view, the Edit, Find, Find advanced option was unrecognized and performed no function. (Bug #12884864)
  • A previously selected object could not be dragged, as it would instead enter "Edit Name" mode after the second click. (Bug #12884796)
  • New server instances created by the Manage Server Instance wizard would send the incorrect service name to the MySQL admin. The command is now constructed at run time using the service name from the server instance profile. (Bug #12567371)
  • The Alter Table... option did not function on tables with triggers. (Bug #12546727, Bug #61110)
  • Creating a server instance using unicode characters worked, but an error would be generated while attempting to open them. (Bug #63100, Bug #13350556)
  • Using Alter routine to make changes would sometimes crash after clicking Apply. (Bug #63076, Bug #13340307)
  • On Microsoft Windows, upgrading MySQL Workbench required MySQL Workbench to be run as a user with Administrator rights. (Bug #62709, Bug #13116366)
  • Opening model files while using a MySQL Workbench version that was installed over a previous MySQL Workbench installation would sometimes cause permission issues. The workarounds included running MySQL Workbench with administrator privileges, or removing the installation folder before upgrading. (Bug #62703, Bug #13323929)
  • An unhandled exception might be emitted after modifying an EER diagram, with a popup window reading "MySQL Workbench has encountered a problem - Queue empty." (Bug #62651, Bug #13079826)
  • A query history date would incorrectly change when a history entry, other than the last one, was selected when the query was executed. (Bug #62642, Bug #13104635)
  • The Create Routine... feature would report that it created a routine, but it did not, and the error was revealed in the output window. (Bug #62624, Bug #13362190)
  • The Server Administrator did not function with MySQL Server 5.0. And although MySQL Workbench does not officially support MySQL Server 5.0, this functionality now works. (Bug #62549, Bug #13029339)
  • The Reconnect to DBMS toolbar option would not reconnect after unchecking the Safe Updates preference. A workaround is to uncheck this option, then restart MySQL Workbench. (Bug #62448, Bug #13014798)
  • Expanding then collapsing the query results window within the SQL editor, yielded a different appearance. (Bug #62371, Bug #13007096)
  • On Ubuntu 11.10, MySQL Workbench would freeze at the startup splash screen. (Bug #62347, Bug #13099521)
  • The Configuration File path within the Server Administration panel is now read-only, when before it would temporarily set the path. This path should be set via the profile setting instead. (Bug #62252, Bug #12922746)
  • Fixed a typo, where "database" was misspelled as "dabase" within the DBDesigner description. (Bug #62250, Bug #12912465)
  • The Auto-save feature would behave with unpredictable results, by opening up an incorrect number of windows when MySQL Workbench was next loaded. (Bug #62192, Bug #12907612)
  • Opening Management, Server Logs would generate an unhandled exception when using table-based logging, while the general log was empty. (Bug #62123, Bug #12872836)
  • After setting a default schema, choosing Refresh all while the schema information is "fetching" would result in an unhandled exception. (Bug #62086, Bug #12913399)
  • Switching between two logins for a single database connection required the password to be reentered with each switch. (Bug #62052, Bug #12921420)
  • On Linux, the Database, Generate Catalog Diff Report... model option was disabled. (Bug #62040, Bug #12844314)
  • Within the Routine Editor, opening multiple Apply SQL Script to Database dialogues and then executing one, except for the last one opened, would crash MySQL Workbench. (Bug #61988, Bug #12918227)
  • On Microsoft Windows, the EER diagram search did not work across multiple pages. (Bug #61957, Bug #12818216)
  • Fixed Data export so that routines and views are only exported when they are selected. In addition, individual views may now be selected for export. (Bug #61937, Bug #12949918)
  • Importing a dump would misquote the --defaults-extra-file option, which would cause the import to fail. (Bug #61910, Bug #12912786)
  • A Download Prerequisites link is now displayed when prerequisites, such as the "Visual C++ 2010 Redistributable Package" requirement, are not met. Before, the link was not visible. (Bug #61897, Bug #12769499)
  • Repeatedly refreshing a schema resulted in an unhandled exception. (Bug #61892, Bug #12762893)
  • The File, Open Recent feature would open the incorrect script. (Bug #61856, Bug #12912374)
  • On Mac OS X, switching from the Model tab to the EER Diagram tab caused an error sound. (Bug #61809, Bug #12757337)
  • File, Export, Forward Engineer SQL CREATE Script would append an extra space to TINYINT(1) after converting it from BOOL. (Bug #61696, Bug #12711138)
  • On Microsoft Windows 7, some MySQL Workbench buttons would be difficult to read due to incompatible background colors with the "Windows classic Style" scheme. (Bug #61685, Bug #12711145)
  • MySQL Workbench would not recognize the active schema with case insensitive servers. As a result, an active schema within the Object browser would be unselected after a USE statement was executed. (Bug #61641, Bug #12711143)
  • The Users and Privileges window did not scale to low screen resolutions like 1024x768. It does now, although MySQL Workbench still has an official minimum screen resolution of 1280x800. (Bug #61518, Bug #12661556)
  • Tab panels within Server Administration would not fresh properly. (Bug #61452, Bug #12647731)
  • The Object editors (such as Alter Table, Alter View, and Alter Routine) now open as tabs, instead of separate wizard windows. (Bug #61422, Bug #12642157)
  • Exporting SQL for tables that included comments would generate invalid SQL statements. A comma was missing immediately before the COMMENT. (Bug #61393, Bug #12627762)
  • After opening a saved model file, the Control+T shortcut would not work from within a query window. (Bug #61379, Bug #12627716)
  • MySQL Workbench could crash while restoring large files. (Bug #61365, Bug #12627685)
  • The Clear script output and Close this script tab buttons are now disabled in non-script tabs. (Bug #61318, Bug #12616331)
  • On Linux, code folding for stored procedures and loops did not work properly within the SQL editor. (Bug #61302, Bug #12612394)
  • Pressing Execute after double clicking and editing a field in select all mode, resulted in an unhandled exception. (Bug #61279, Bug #12627523)
  • On Microsoft Windows, the Find option (Control+F) for the SQL editor was not available. (Bug #61233, Bug #12622697)
  • Executing a slow query would not notify the user that the query was running. The new SQL editor interface does show the progress. (Bug #61231, Bug #12589710)
  • When hovering the mouse pointer over a table figure on a diagram, the foreign key tooltip would hide the table column names. (Bug #61055, Bug #12546715)
  • The default schema selection would be lost after synchronizing a model. (Bug #60975, Bug #12621744)
  • MySQL Workbench would sometimes crash while in Forward Engineering mode. (Bug #60950, Bug #12572071)
  • On Linux and Mac OS X, using Tab and Shift+Tab to jump to next/previous fields has been added to the query result view. It had previously only worked on Windows. Additionally, the Escape key will now cancel editing of the current cell, and PageUp/PageDown scrolls one page up and down in the result set. (Bug #60865, Bug #12368205)
  • Manipulating multiple SQL editor tabs would sometimes result in uncaught exceptions. (Bug #60764, Bug #12621640)
  • MySQL Workbench would crash when attempting to use Alter Table or Create Table from within the context menu. (Bug #60760, Bug #12621510)
  • Fixed a crash bug, which would happen on exit. (Bug #60733, Bug #12632325)
  • If a schema within the schema panel was clicked, then a table was also clicked (dropped down) within the schema, then the panel containing Actions, Schemas, and details would expand to fill half of the view window, and the size could not be adjusted. (Bug #60692, Bug #12587848)
  • The Generate INSERT Statements for Tables option would not generate INSERT statements for BLOG columns. (Bug #60657, Bug #12565791)
  • Factory snippet files were fixed, to include proper line-endings for all platforms. (Bug #60643, Bug #12621434)
  • Closing MySQL Workbench would not prompt to save unsaved work from modified SQL files and windows. (Bug #60557, Bug #11926868)
  • The SQL editor output tab did not report the number of affected rows. (Bug #60535, Bug #12617147)
  • The Syncronize model with Database wizard would not properly handle case-sensitive table names. (Bug #60523, Bug #12617135)
  • Open diagram tabs from a saved MySQL Workbench state were not saved properly. (Bug #60515, Bug #12617096)
  • The Advanced Export Options preferences were not saved, and would reset after restarting MySQL Workbench. (Bug #60497, Bug #11889197)
  • Connection and query tabs can now be reordered, by dragging and dropping with the mouse pointer. (Bug #60409, Bug #11865602)
  • On Linux, viewing the embedded documentation required the python-sqlite2 package. (Bug #60336, Bug #11874507)
  • On Mac OS X, Command+W will now close the active script editor tab, and Command+Shift+W will now close the active connection tab. This is now consistent with behavior on other operating systems. Before, the Command+W combination closed the active connection tab. (Bug #60253, Bug #11829750)
  • Pressing Esc once now escapes out of edit mode within the row editor. Before, it had to be pressed twice. (Bug #60131, Bug #11829997)
  • The Copy Row Content option would throw an unexpected exception, from within a model.
  • In addition, the Paste Row option was added. (Bug #60116, Bug #12417533)
  • The USE statement is now properly quoted. For example, an invalid USE query would be generated if a schema contained a - character. (Bug #59882, Bug #11766711)
  • Copying a table column would lose the data type, when only the column line number was selected instead of the data type or field name. (Bug #59285, Bug #11905520)
  • Within a server instance administration panel, setting Export to Self-Contained File to an invalid path resulted in an unhandled exception. (Bug #59246, Bug #11766194)
  • The Output tab of the SQL editor now adjusts whitespace characters, as to display queries on a single line. (Bug #58989, Bug #11765966)
  • Enabling the Limit Rows SQL editor preference would cause invalid SQL syntax with SELECT INTO statements. (Bug #58732, Bug #11765738)
  • When viewing text at a size greater than 100% (such as 125%), some text field labels would be partially hidden. (Bug #58408, Bug #12628507)
  • Server Administration, Manage Import/Export would return an error about the dump module. (Bug #58098, Bug #11765164)
  • MySQL Workbench would allow the creation of foreign keys on tables using engines that do not support them. A warning is now emitted if this is attempted. (Bug #57875, Bug #11764972)
  • MySQL Workbench did not fully adhere to locale settings, which could result in unhandled exceptions. (Bug #56869, Bug #11764077)
  • The Foreign Keys tab of the Alter Table wizard only created an index, without the foreign key. (Bug #56818, Bug #11764033)
  • Broken views (e.g., a column no longer exists) are now displayed as broken within the schema tree view. (Bug #56701, Bug #11763928)
  • Using MySQL Workbench could result in an unhandled exception, with the message "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." (Bug #56034, Bug #11763338)
  • Editor windows would sometimes lose focus, but they are now docked within the main application window, which eliminated this problem. (Bug #55923, Bug #11763235)
  • Auto-scrolling for the SQL output and history windows was added. (Bug #55865, Bug #11763183)
  • The Find feature (search) was replaced with a panel, which offers more consistent behavior across platforms. The Find and Replace feature is also now a panel, instead of a pop-up window. (Bug #54765, Bug #11762197)
  • On Linux, the previously set window positions and sizes were not saved by MySQL Workbench. These settings are now saved upon closing, and used when MySQL Workbench is loaded. (Bug #54025, Bug #11761521)
  • The Finish button was inactive (grayed out) for the Edit Table Data dialog, if the database contained exactly one table. (Bug #52833, Bug #11760422)
  • If a table cannot be edited (e.g., no Primary key), then MySQL Workbench now notifies users of the reason, when before the edit option was simply not available. (Bug #51563, Bug #11759263)
  • Closing and opening the SQL Editor now sets the last used schema as the default, instead of the schema specified within the connection. (Bug #51454, Bug #51026, Bug #11759165, Bug #11758776)
  • A triple-click was required to change the Referenced column of a foreign key, while editing a table within an EER diagram. (Bug #50725, Bug #11758512)

New in MySQL Workbench 5.2.34 (May 26, 2011)

  • Functionality added or changed:
  • The Check for updates... menu item that was removed several releases ago has been restored. (Bug #60488, Bug #11879029)
  • If a column value is too long to display, an ellipsis (...) is displayed at the end to indicate that there is more data. (Bug #55976, Bug #11763283)
  • MySQL Workbench now shows query execution time. (Bug #51199, Bug #11758933)
  • The SQL Editor can now wrap long text lines. This is controllable per editor instance using its context menu. By default, line wrapping is off. (Bug #50569, Bug #11758372)
  • Bugs fixed:
  • Beautify Query mishandled queries containing table aliases. (Bug #11883490)
  • File import operations failed with these errors:
  • Error executing task: 'module' object has no attribute'STARTF_USESHOWWINDOW' Error executing task local variable 'p1' referenced beforeassignment
  • (Bug #60982, Bug #12430815)
  • Multiple USE commands to change databases in the SQL Editor caused MySQL Workbench to crash. (Bug #60856, Bug #12358480)
  • MySQL Workbench could not view the server logs if the server was configured with log output set to 'TABLE,FILE'. (Bug #60853, Bug #12365454)
  • Find did not work in Query tabs. (Bug #60787, Bug #12347063)
  • Changing connection parameters in Synchronize Model resulted in an error message. (Bug #60771, Bug #12329285)
  • For import and export command operations using a Unix socket file, MySQL Workbench added an incorrect --pipe option to the command. (Bug #60756, Bug #12325422)
  • Forward Engineer SQL Script wizard wrote incomplete output. (Bug #60751, Bug #12329302)
  • Beautify Query incorrectly removed spaces between table names and table aliases. (Bug #60742, Bug #12327013)
  • New server instances were not always displayed in the Server Adminstration list. (Bug #60684, Bug #11933087)
  • On Linux, MySQL Workbench was overly aggressive about reading schema information from INFORMATION_SCHEMA, leading to slowdowns when connecting to the MySQL server. Now information is read only for the default schema. (Bug #60644, Bug #11926793)
  • Control+S did not save models or SQL Editor scripts. When opening an SQL script, it did not display the filename. (Bug #60594, Bug #12402774)
  • MySQL Workbench could crash trying to display result sets that contained binary data. (Bug #60588, Bug #12385959)
  • The SQL statement generated by clicking an item in the action pane failed to include the qualifying database name. (Bug #60562, Bug #11926864)
  • The Administrator panel would not load for large process ID values of the MySQL server. (Bug #60505, Bug #12397312)
  • MySQL Workbench crashed trying to execute some CREATE TABLE statements. (Bug #60475, Bug #12356405)
  • Clicking on a user name to obtain details caused MySQL Workbench to crash if the name contained an apostrope. (Bug #60473, Bug #11889207)
  • Query results could not be saved to a directory for which the name contained Japanese characters. (Bug #60438)
  • Exporting query results after entering a file path name did not work. (Bug #60438, Bug #11868335)
  • Multiple-selection copy did not work. (Bug #60410, Bug #11865601)
  • MySQL Workbench failed to compile on Gentoo Linux. (Bug #60358, Bug #12368202)
  • Stored procedures could not be opened from the objects tree if the SQL Delimiter had been changed to the ';' character. Now the label for this option in the Preferences dialog has been changed to Non Standard SQL Delimiter to better reflect its actual meaning. The tooltip has also been changed to be more descriptive. In addition, if an Alter ... operation fails due to a parse error, the retrieved DDL code is shown as is in the SQL editor. (Bug #60354, Bug #11889184)
  • Attempting to connect to a nonexistent server put MySQL Workbench in a nonresponsive state. (Bug #60329, Bug #11834154)
  • Record set export to a file failed unless the file name was given as an absolute path name. (Bug #60256, Bug #11874435)
  • Output from the routine editor added excessive blank lines between routine definitions. (Bug #60205, Bug #11874345)
  • When database connections had process IDs with large values, the connection tab displayed an error box rather than process information. (Bug #60192, Bug #12397794)
  • Items from the SQL Editor history were not always available to be copied into the SQL script. (Bug #59807, Bug #1766651)
  • It was not possible to import a dump if MySQL Workbench was installed in a directory having a name that contained spaces. (Bug #59737, Bug #11766595)
  • The description given in the Workbench Preferences dialog for the --safe-updates option was incorrect. (Bug #59370, Bug #11766289)
  • Connection sorting was lost after a status refresh. (Bug #59355, Bug #11766279)
  • The Users column in the Schema Privileges tab was not sortable. (Bug #59138, Bug #11766100)
  • When the user closed the main window with a connection active, MySQL Workbench did not terminate the connection. This lead to Aborted_clients errors on the server side. (Bug #58944, Bug #11765929)
  • Opening a connection twice resulted in unexpected errors when executing queries on the connection. (Bug #58835)
  • When double clicking tables in a model diagram, tabs were mismanaged such that the proper set of tabs did not remain available. (Bug #57349, Bug #11764509)
  • On Mac OS X, Option+Delete functioned as Undo rather than deleting the word to the left of the cursor. (Bug #57184, Bug #11764360)
  • If MySQL Workbench finds that .NET is not installed, it now provides a link for the user to get the .NET instaler. (Bug #55145, Bug #11762538)
  • On Mac OS X, two-finger scrolling did not work in query windows. (Bug #53678, Bug #11761211)
  • The TRIGGER privilege could not be assigned at the schema level. (Bug #52977, Bug #11760556)
  • It was not possible to view or edit long text lines with the inline editor. (Bug #52087, Bug #11759751)
  • On Windows, a packaging error for the Zip file distribution led to spurious GRT Shell warnings at MySQL Workbench startup. (Bug #49813, Bug #11757719)
  • For SQL Editor tabs where the connection had no name, connection information was not shown. Now the hostname is shown (up to 21 characters). (Bug #49058, Bug #11757060)

New in MySQL Workbench 5.2.33 (Mar 16, 2011)

  • Bug #60370 Error in securityManager module: error calling WbAdmin…
  • Bug #60396 SQL script generation not working
  • Bug #60369 Cannot open saved work bench file
  • Bug #56456 Users not sorted for schema privileges
  • Bug #59315 Kill Query SQL Error 1064
  • Bug #59774 Crash when closing query results tab
  • Bug #59932 List of EER diagrams is not updated when diagram is deleted, causing crash

New in MySQL Workbench 5.2.27 (Sep 7, 2010)

  • Functionality added or changed:
  • The Sychronize Model With Database wizard has been changed recently to show all schemata in a model, regardless of whether they exist in the live database or not. In addition, the following changes have been made:
  • The wizard shows a list of schemata that exist in the model but are missing from the live server, with a note recommending the use of the Forward Engineering wizard.
  • The wizard does not auto-select schemata names that are in the model but not in the live database. (Bug#54748)
  • Bugs fixed:
  • (Bug#56020)Forward engineering a model to a live database crashed MySQL Workbench. (Bug#56009)Dump tab did not display the target folder before the dump was performed. (Bug#55945)MySQL Workbench crashed when using the foreign key editor.
  • (Bug#55910)If the sidebar was placed on the right hand side, using the option in Workbench Preferences, then when Add Diagram was double-clicked then the following Unexpected Error was generated: SplitterDistance value is invalid (-52)
  • (Bug#55902)In the SQL Editor, executing statements designed for MySQL Server version 5.5 generated syntax highlighting errors. (Bug#55891)In the SQL Editor, executing statements designed for MySQL Server version 5.5 generated syntax errors. (Bug#55867)If "Dump views" was selected for a backup, the following error was generated: Unhandled exception: global name 'views_by_schema' is not defined
  • It was necessary to restart the Administrator in order to enable the dump facility again. (Bug#55833)In the SQL Editor, right-clicking on a routine name in the Object Browser caused MySQL Workbench to exit unexpectedly. (Bug#55822)MySQL Workbench crashed when using the Partitioning tab of the Table Editor. (Bug#55761)If a table was copied in the EER Diagram view, and then the model synchronized with the live database, the synchronize functionality did not recognize the copied table as a new table, and overwrote the original table. (Bug#55566)Renaming a column with a foreign key resulted in an invalid script being generated on forward engineering or synchronization with a live database. (Bug#55502)On the second attempt to save a read-only model file, the following error was generated: Couldn't backup existing file name-of-the-file.mwb: No such file or directory
  • (Bug#55439)When a table was being edited in the Table Editor, and its name changed, the change of name was not reflected on the Table Editor's table tab. (Bug#55338)It was not possible to add LOCK TABLES privilege when assigning a new role in the Model Overview, as that privilege was missing from the available options. (Bug#55186)The schema collation was not saved after being changed in the Table Editor. (Bug#55152)When using MySQL Workbench to report a bug, it was not possible to attach a file using the Choose File button. When the button was clicked, it had no effect. (Bug#55112)It was not possible to dump tables or schemata without the LOCK TABLE privilege.
  • (Bug#55019)Selecting Validate (SQL) from the Model menu and then selecting the Validate All option reported no errors. Selecting Forward Engineer from the Database menu and selecting Run Validations also reported no errors.
  • (Bug#54985)If the Check Duplicated Identifiers (Additions) operation was selected from the Validation (SQL) submenu of the Model menu then the following error message was displayed: Type mismatch: expected object of type db.Schema, but got workbench.physical.Model
  • (Bug#54968)MySQL Workbench caused Windows XP to reboot if launched from Start, Programs, MySQL, MySQL WorkBench 5.2 OSS.
  • If a MySQL Workbench model file (.mwb) was opened directly, an error dialog titled Microsoft Visual C++ Runtime Library was displayed with the message: An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information.
  • The dialog's only option was OK. After clicking OK, two more instances of the same dialog were displayed. After clicking OK for all three, MySQL Workbench opened with the model file displayed.
  • On Windows 7 x64 the same run-time error (R6034) occurred. (Bug#52949)

New in MySQL Workbench 5.2.22 RC (Jun 21, 2010)

  • Functionality added or changed:
  • On Linux, MySQL Workbench automatically added a .sql extension, where an extension was not specified, to any script file saved from the SQL Editor.
  • MySQL Workbench has been changed so that on Linux a .sql extension is not automatically added. However, on Windows the file extension is added if one is not specified. (Bug#53731)
  • MySQL Workbench has been changed so that only the Model Overview tab indicates that changes need to be saved, using an asterisk, rather than this being reflected on individual EER Diagrams. (Bug#53042)
  • The SQL Editor now includes a new context menu item Set as Default Schema. This is applicable to schema nodes in the Object Browser and the Overview panel of the Query Editor. Previously the only way to change the default schema was to select the schema from the schema selector drop-down listbox located at the top of the Object Browser. (Bug#51479)
  • MySQL Workbench now supports entering of expressions such as DEFAULT or CURRENT_TIMESTAMP into the inserts editor. The expression needs to be preceded by \func. (Bug#36206)
  • Bugs fixed:
  • If a property value was changed in the Workbench Preferences dialog, and OK clicked, or a new tab clicked before the cursor was moved away from the value being changed, then the change was silently reverted. (Bug#54060)
  • If the Manage Server Instances dialog was launched, and either the New or Delete button clicked, and then the dialog closed, MySQL Workbench crashed if the New Server Instance action item was then clicked on the Home screen. (Bug#54028)
  • Gnome keyring package was a dependency of MySQL Workbench. It was undesirable to require its installation on KDE-based systems. (Bug#54010)
  • When MySQL Workbench was launched, an overlay was displayed. In the application bar the dialog prompting for the keyring password was waiting for input but it was not possible to enter the password as the overlay hid the dialog. (Bug#53974)
  • On the Model Overview page, when a new user object was created with Add User in the Schema privileges section, it was not possible to change any of the user object's attributes. For example, if the name of the object was changed, and entered, it would then change back to its original setting. (Bug#53946)
  • In the EER Diagram view heavy flicker resulted if the cursor was held over relationship lines or tables. (Bug#53941)
  • When a table containing triggers was loaded into the Alter Table dialog of SQL Editor, clicking on the Triggers tab showed an empty trigger, rather than the correct trigger code. (Bug#53940)
  • In the SQL Editor, performing a query on a remote server returned BLOB values for columns that were not of type BLOB.
  • Since binary byte strings tend to contain null bytes in their values, for safety reasons they were not displayed in the results grid. They could only be viewed or edited by means of the BLOB editor to avoid data truncation.
  • MySQL Workbench has been changed to include a new global option which has been added to the SQL Editor tab of the Workbench Preferences dialog. The option is “Treat BINARY/VARBINARY as non-binary character string”. By default it is not selected. (Bug#53920)
  • Attempting to copy objects from an existing diagram to a new diagram resulted in the following error: OverviewBE::get_node: invalid node 1.0.0.22. (Bug#53914)
  • In the SQL Editor, the context-sensitive menu options Copy to Clipboard and Send to SQL Editor both failed to work. This applied to both copying in the Object Browser and in the Overview tab. (Bug#53903)
  • In the SQL Editor, when deleting a snippet from the snippet list using the toolbar button, the first snippet was deleted, regardless of which snippet was selected. (Bug#53860)
  • When forward engineering a schema to a database with the DROP Objects Before Each CREATE Object option selected, the DROP statement used a delimiter before it had been declared. (Bug#53853)
  • In the SQL Editor, if code was typed into the SQL Query tab, and then the application exited, MySQL Workbench did not prompt the user regarding unsaved changes, and so any code typed into the SQL Query tab, and not saved, was lost. (Bug#53848)
  • In the SQL Editor, when renaming views or routines using the live editor, the generated ALTER script contained only drop statements, CREATE statements being omitted. (Bug#53847)
  • In the SQL Editor, when attempting to change an index from INDEX to UNIQUE using the Alter Table dialog, no changes were applied, and the following error message was generated: No changes to object were detected. (Bug#53787)
  • In the Create Schema dialog of the SQL Editor, when a new schema name was entered, and changes applied, the schema name appeared to revert to the default name new_schema, rather than being changed to the newly specified name. This only happened on Mac OS X. (Bug#53764)
  • In the SQL Editor, if two procedures were defined in a script, each proceded with a suitable DROP statement, then when the script was executed and the procedures already existed a procedure already defined error occurred. It appeared that the second DROP statement was being ignored. This happened if the line preceding the second DROP statement was terminated with a space, which caused the DROP statement to be ignored, resulting in the error. (Bug#53760)
  • In the SQL Editor, with multiple tabs open, if the script in each tab was saved to a file in turn, the script was actually saved over the previously saved script, resulting in the loss of that script. (Bug#53733)
  • If multiple SQL Query tabs were opened in the SQL Editor, then when a snippet was saved to the snippet list, the snippet saved would always be from the last opened SQL Query tab (the furthest to the right), rather than the currently selected tab. (Bug#53713)
  • In the Columns tab of the Table Editor, if typing in lower case the data type of the column was not automatically completed.
  • MySQL Workbench has been changed so that it now automatically completes the data type regardless of whether the user types upper or lower case letters. (Bug#53710)
  • Compiling MySQL Workbench from source code failed with the following errors:
  • ...
  • -I../../library/dbc/src -I../../library/vsqlite++/include -D_FORTIFY_SOURCE=2 -O2
  • -fno-strict-aliasing -fwrapv -march=x86-64 -gdwarf-2 -g2 -Wextra -Wall -Wno-unused
  • -Wno-deprecated -ggdb3 -DENABLE_DEBUG -MT canvas_floater.o -MD -MP -MF
  • .deps/canvas_floater.Tpo -c -o canvas_floater.o `test -f 'model/canvas_floater.cpp' ||
  • echo './'`model/canvas_floater.cpp
  • model/canvas_floater.cpp: In constructor 'wb::Floater::Floater(mdc::Layer*, const
  • std::string&)':
  • model/canvas_floater.cpp:65:59: error: cannot call constructor 'mdc::Color::Color'
  • directly
  • model/canvas_floater.cpp:65:59: error: for a function-style cast, remove the redundant
  • '::Color'
  • make[3]: *** [canvas_floater.o] Error 1
  • make[3]: Leaving directory
  • `/home/users/Arvenil/rpm/BUILD/mysql-workbench-oss-5.2.21/backend/wbprivate'
  • make[2]: *** [all-recursive] Error 1
  • make[2]: Leaving directory
  • `/home/users/Arvenil/rpm/BUILD/mysql-workbench-oss-5.2.21/backend'
  • make[1]: *** [all-recursive] Error 1
  • make[1]: Leaving directory `/home/users/Arvenil/rpm/BUILD/mysql-workbench-oss-5.2.21'
  • make: *** [all] Error 2
  • (Bug#53687)
  • In the Data Dump tab of the Administrator, the Options panel was not rendered correctly. (Bug#53681)
  • In the SQL Editor, if a query was executed, and then interrupted, MySQL Workbench hung. (Bug#53652)
  • If a query was typed in the SQL Query tab, and then cmd + Enter immediately pressed to execute the query, the query failed. This only happened on Mac OS X. (Bug#53650)
  • In the Create New Server Instance Profile wizard, on the Operating System page the MySQL Installation Type drop-down listbox was not populated correctly. Although all items were initially correctly displayed, if the Back button was clicked, and then Next clicked to return to the page, all the items in the list were duplicated. Each time this process was repeated the original list items would again be duplicated. (Bug#53649)
  • On the Home screen, the MySQL Team Blog and Workbench Team Blog icons linked to the same page. Further, the MySQL News Letter icon linked to the MySQL Developer forum. (Bug#53628)
  • In the SSH Shell Connection panel of the Manage Server Instances dialog, if any port other than 22 was specified it was subsequently ignored. (Bug#53623)
  • The MySQL configuration file was corrupted by the Administrator when changes were applied, if the configuration file was not terminated with a new line. (Bug#53620)
  • In the SQL Editor, the toolbar items on the Snippets tab to replace and insert snippets had no effect when clicked. (Bug#53610)
  • Specifying a new font for the SQL Editor's SQL Query tab contents had no affect on appearance. (Bug#53605)
  • In the Data Dump section of the Administrator, when an export was generated the following error occurred:
  • mysqldump: Error 2020: Got packet bigger than 'max_allowed_packet' bytes when dumping
  • table 'xxx' at row: 1
  • This only happened for larger tables. (Bug#53599)
  • MySQL Workbench crashed when attempting to connect to a Linux server using an SSH connection. (Bug#53476)
  • When a model containing a stored procedure was forward engineered to a script, the script contained invalid SQL code. This happened when the DROP Objects Before Each CREATE Statement and Export MySQL Routine Objects options were selected. Problems that occured with the SQL code included a delimiter being used before its definition and also DROP statements not being terminated. (Bug#53467)
  • MySQL Workbench crashed on selection of menu item Model, Create Diagram from Catalog Objects. (Bug#53454)
  • It was not possible to edit schema properties, such as name and default collation, in the schema editor. (Bug#53438)
  • When a model containing a table using a 1:n relationship was synchronized with a live database, the relationship then failed to render in the EER Diagram. (Bug#53252)
  • When a large script was loaded into the SQL Editor, an out of memory exception occurred.
  • Inefficient end of line conversion in MySQL Workbench was the cause of memory exhaustion. The SQL Editor has been enhanced to support custom end of line formats and now preserves original line endings used in the file. End of line conversion is not used any more and loading of big files can be done faster and more efficiently. (Bug#53190)
  • In the Manage DB Connections dialog, selecting the Use ANSI quote to quote identifiers had no effect with respect to subsequent queries using that connection. (Bug#53160)
  • Delimiters were erroneously added to trigger code if the currently selected schema was changed. (Bug#53151)
  • In the Triggers tab of the Table Editor, if a trigger was written that contained a DROP TRIGGER statement, the statement was automatically removed. (Bug#53023)
  • MySQL Workbench generated an exception when an attempt was made to change the configuration file in the System Profile tab of the Manage Server Instances dialog. (Bug#52947)
  • In the Alter Table dialog of the SQL Editor, when a comment was entered for a column in the Comments tab, and the changes applied, the comment was not saved. (Bug#52893)
  • Setting WB_NO_GNOME_KEYRING=1 on Kubuntu did not appear to disable the Gnome keyring, it was therefore impossible to connect without an active keyring daemon. (Bug#52866)
  • When scrolling in an EER Diagram, MySQL Workbench repeatedly displayed an error dialog containing the message “OpenGL error: invalid value”. (Bug#52840)
  • In the Data Dump section of the Administrator, when a schema was dumped to multiple files, the stored routines were not exported. (Bug#52798)
  • It was not possible to set ON UPDATE CURRENT_TIMESTAMP as the default value for a column. (Bug#52350)
  • If a table was dragged from the catalog tree on to the EER Diagram, then the catalog tree collapsed. (Bug#51862)
  • In the Connections tab of the Administrator, queries containing a comment did not always display correctly in the Info column. (Bug#51848)
  • Output did not scale correctly when printing sizes other than A4. (Bug#51515)
  • When synchronizing to a live database, triggers showed as requiring updating, even when the model and live database were identical. (Bug#51409)
  • If a SQL file, using Windows file format, was loaded into the SQL Editor, it was displayed with additional line breaks, and the SQL code was not interpreted correctly. Further, if code written in the SQL editor was saved to a file and then opened in an editor on Windows, it contained additional line breaks. (Bug#51308)
  • In the Connections tab of the Administrator facility, hostnames were sometimes not displayed correctly. This happened if the hostname contained a '-' character. (Bug#51119)
  • In the SQL Editor, if the Add Table facility was used to create a new table with the same name as an existing table, then after changes were applied, the content of both tables was the same as the existing table, and changes unique to the second table were lost. (Bug#51107)
  • When an attempt was made to forward engineer a project which contained a view, it failed with the following error:
  • ERROR: Error 1046: No database selected
  • (Bug#51091)
  • Inserts added to a model and saved on Windows were not visible when that model was loaded on Mac OS X. (Bug#51029)
  • In the SQL Editor, carrying out a SELECT on a table containing more than 1000 columns resulted in the error 'Too many SQL variables'. (Bug#50952)
  • In the Model Overview page, when small icons view was selected, if table names were truncated, there were no tooltips to allow visibility of the full name. The tooltips however were present for the large icons view, and the details view. (Bug#50739)
  • MySQL Workbench reported a server as not running, even though the server was correctly running. MySQL Server concerned was running on Windows 7, 64-bit. (Bug#50585)
  • In the EER Diagram view, it was not possible to paste a copied layer. The paste menu item was disabled in the context-sensitive menu and main menu, and also pressing Ctrl+V had no effect. (Bug#50253)
  • In the EER Diagram view, when the diagram was displayed over multiple pages, the gray line dividing pages in the Navigator was not visible in the diagram itself. (Bug#50243)
  • In the EER Diagram view, when zoomed out, a layer could be placed beyond the diagram's perimeter at the bottom right. Further, if a layer was placed beyond the perimeter at the top left, it snapped back within confines of the diagram correctly, but the navigator view was not updated accordingly. (Bug#50242)
  • Zooming out from a diagram in EER Diagram view resulted in severe flicker. (Bug#50240)
  • In SQL Editor, when using the Alter Table facility to set a column to Auto Increment (AI), the dialog reported that “No changes to object were detected”. (Bug#50214)
  • When using Create EER Model from SQL Script from the Home screen, the specified engine type was not present in the resultant EER model. (Bug#49568)

New in MySQL Workbench 5.2.17 Beta 7 (Apr 5, 2010)

  • Fixes for 69 bugs. P1 -4, P2 – 21 , P3 – 41 and P4 – 3.
  • New Windows UI components
  • New “look” for windows version
  • Modern style tab-controls
  • New UI, toolbars and sidebar-placements
  • Easier to use
  • Improved look and feel
  • Distinct User Snippets
  • Pre-Loaded DML and DDL Snippet Libraries
  • SQL Editor:
  • All DDL Statements for changes are available.
  • Results menu bar
  • In Output - added Details Pane for Action and Message

New in MySQL Workbench 5.1.10 Beta 2 (Apr 10, 2009)

  • Fixed several bugs and added some enhancements that to the Interface. There’s a new editor for defining/maintaining User Defined Datatypes.