|
What's new in this version: MySQL Workbench 8.0.16
Functionality Added or Changed:
- The script editor now highlights matching pairs of parentheses when one of the pair is selected
- 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
- MySQL Enterprise Firewall could not be installed from the Enterprise Edition of MySQL Workbench
- An incorrect-integer-value error resulted when the Table Data Import Wizard attempted to import CSV data to a valid database table
- 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
- 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
- The LATERAL keyword now conforms with the SQL editor convention to highlight and indent the words considered keywords by MySQL
- 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)
- An error in the generated mysql_rdbms_info.xml file caused MySQL Workbench to stop working
- 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
- With the GNOME desktop theme set to Adwaita (default) or Adwaita-dark, text selected within the SQL editor was invisible
- 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
- Executing a function or stored procedure caused an unexpected program shutdown on Linux hosts
- The SQL beautifier feature produced no change when it was executed within the Triggers tab of the table editor
- 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
- An exception was generated when the results of a query was toggled between visual explain and tubular explain formats within the Execution Plan tab
- A user account that was deleted properly from Users and Privileges remained visible until the Administration tab closed and reopened
- 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
- Records imported from an external file, such as a CSV file, generated an exception when the operation was attempted from a macOS host
- 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
- 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
- Some keyboard shortcuts, such as Command-C, did not work within the SQL and model editors on macOS 10.14 hosts
- Rather than generating a warning or error when it detected an unknown SSH option in the ~/.ssh/config file, MySQL Workbench became unresponsive
- 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
- 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
- The actions selected from the history-palette context menu did not produce any results
- The code auto-completion feature in the query editor did not provide the expected behavior
- 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
- MySQL Workbench stopped working on Linux hosts after a long period of use that included adding new tables to an existing model
- 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
- 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
- Some keyboard shortcuts were unsuccessful when used properly
- 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
- The template that was generated for a table of a model did not include type values within the Datatype column
- Items listed within the Schemas tab were not visible when selected on Linux
- 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
- 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
- The operation to check for MySQL Workbench updates (from Help) returned an error when used behind a proxy server with authentication
MySQL Workbench 8.0.15
- This release contains no functional changes and is published to align version number with the MySQL Server 8.0.15 release
MySQL Workbench 8.0.12
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`
- 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)
MySQL Workbench 6.3.10
Bugs Fixed:
- Performance information within the Administration – Dashboard tab demonstrated a slow rate of refresh on hosts running macOS High Sierra
- 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
- 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
- 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
- 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
- Performing a keyword search in the EER Diagram Editor on hosts running macOS High Sierra caused MySQL Workbench to exit unexpectedly
- Forward engineering a physical database design did not operate as expected on hosts running macOS High Sierra
MySQL Workbench 6.3.9
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.
MySQL Workbench 6.3.8
- Change log not available for this version
MySQL Workbench 6.3.7
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.
Bugs Fixed:
- A typo was fixed on the Configure Server Management page.
- On OS X, after creating a new model, and new diagram, right-clicking on the empty diagram background would freeze Workbench.
- Executing Data Import/Restore would emit an unhandled exception with Import from Self-Contained File enabled.
- On Linux, the Table Data Export wizard failed to complete the export process.
- The MySQL Enterprise Backup Restore functionality could emit an unhandled exception under some circumstances.
- Editing a remote MySQL options file via the Options File management tool would emit an unhandled exception after clicking Apply.
- Exporting data to JSON was exporting NULL values as NULL instead of null, thus breaking the JSON output.
- Under Users and Privileges, Workbench did not allow hyphens for host names in the "limit to hosts matching" field.
- When viewing the code for an existing view (SQL to create the view), hexadecimal values were truncated.
- 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.
- 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.
- The Schema filter was slow (poor performance) when a lot (1000+) of schemas were present.
- 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
- The generated SQL generated by the forward engineering wizard would incorrectly output "VIRTUALCOMMENT" instead of "VIRTUAL COMMENT".
- An new option is available to specify a path to the SSH configuration and/or known hosts file. This option overwrites the defaults.
- 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.
- Under Reverse Engineering, the information provided in the wild card description to select objects contained a typo.
- After successfully executing the database migration wizard, executing it a second time required Workbench to be restarted.
- When executing Data Export using a remote MySQL connection, the error resulting from a missing mysqldump binary was unclear.
- The PostgreSQL migration wizard could fail to migrate PostgreSQL databases that were generated with tryton.
- The Dashboard and Server Status reported different Select per second values. The Server Status page reported incorrect (inflated by about 3x) values
- The PostgreSQL migration wizard could fail with an "pg_catalog.pg_enum does not exist" error.
- 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.
- 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.
- 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.
- Import and export to JSON format failed if the table had column names that were keywords such as key or value.
- 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".
- 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".
- All generated paths now will use "/" as the directory separator in order to avoid the "s" being interpreted as a space, such as "C:pathtocertsserver-cert.pem" for generated SSL certificates.
- 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)".
- With Fabric, Workbench cached the topology information and did not update it when the topology changed, like when switching to a new master.
- 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).
- Some stored procedure definitions were incorrectly reported as having invalid syntax.
- Executing Alter Stored Procedure with a user lacking SELECT privileges would crash MySQL Workbench
- 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.
- 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.
- Some internal Workbench queries failed to execute with sql_mode set to ANSI_QUOTES.
- The Total Time field within the Recent Activity grid of the Online Backup / MySQL Enterprise Backup section of Workbench showed an incorrect duration value.
- 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".
- MySQL Workbench lacked a CentOS profile, so could fail to make remote connections to a CentOS machine.
- 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.
- On Windows, the "DEFAULT NULL" value could unintentionally be removed from the "Alter Table" window when clicking on it.
- The Database Migration migration link on the home page was not functioning immediately after a successful migration.
- Several grammar and spelling corrections were implemented into the GUI.
- Under certain circumstances, sub-queries were reported as syntax errors
- Several SQL Server 2014 database migration improvements.
- While modeling, pressing the Enter key while editing a document's properties would close the document properties window instead of adding a new line
- 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.
- 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.
- Executing Delete Row(s) after selecting more than six rows from the results grid would not delete all of the selected rows.
- Adding a DATETIME with precision (such as DATETIME(3)) from the Table Editor would eventually get reverted to DATETIME (without precision).
- The search (magnifying glass) icon in the schema search field was misplaced after the left sidebar was resized.
- Workbench will now prompt to continue the execution of operations containing loops in stored procedures, instead of just canceling it after ~200 executions.
- 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.
- 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.
- MySQL connections were leaked when connecting and disconnecting to MySQL databases. It leaked one connection per re-connect to a database.
- A large database caused the size reported under the Schema Inspector to wrap around and display a negative number.
- 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".
- The print preview icon dialog was missing the Workbench icon.
- Changes to the modeling Appearance font preference did not save properly, or have an effect.
- On Windows, the Query Stats graph would not render with MySQL Server 5.7.
- The Query Stats information tab was populated even when the Performance Schema was disabled.
- 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.
- 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.
- 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.
- 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=256Kn256K". Workbench now follows MySQL Server behavior, and uses the last defined option.
- The cursor could seemingly disappear after executing a query, as it could remain at its last position when the query started to execute.
- The model Page setup... functionality was not always preserved when choosing a size for printing. |
