This section documents all changes and bug fixes applied since the release of 5.2.19.
Functionality Added or Changed
The SQL Statements tab and the record set data editor tab now indicate when they have unsaved data by displaying an asterisk character. (Bug #52799)
If MySQL Workbench was used on an external monitor as part of an extended desktop, then when the computer was started without the external monitor, MySQL Workbench was not displayed on the primary display, and was therefore invisible. MySQL Workbench now checks for this condition and locates half of the application window on the primary desktop where it can be dragged and resized as required. (Bug #52703)
The foreign key/index mapping implementation has been changed so
that indexes created for foreign keys no longer need be marked
FOREIGN. They now are created with type
INDEX and can be changed to
UNIQUE or other types.
Although the artificial
FOREIGN index type
has been removed, MySQL Workbench still automatically creates and
maintains indexes for each foreign key by naming them after the
keyname and keeping the names (FK to IDX) synchronized.
In the SQL Editor, when a new tab was created, the focus was on the Object Explorer, rather than in the SQL Statements area. This meant that the user had to press the Tab key, or click within the SQL Statements area before they could start typing SQL code. (Bug #50711)
In the Snippets tab of the SQL Editor, there appeared to be a third column, with no heading or data, in the snippets list. MySQL Workbench now expands the second column to fill the available space. (Bug #52559)
In the SQL Editor, when commands were entered into the SQL Statements area, and executed, they appeared on the Output tab. However, when the number of statements appearing in the Output tab exceeded the number that could be displayed in the default area, a vertical scrollbar did not appear. This meant any further statements that were executed were effectively hidden because it was not possible to scroll vertically to display them. (Bug #53156)
In the SQL Editor, field data of type
VARBINARY viewed using the Open
Value in Viewer context-sensitive menu item was
displayed only up to the first null byte (\0).
Script editors, such as the editor in the SQL Editor, that used the Scintilla component, did not have full integration with the Edit menu. Short cuts and menu commands for operations such as copy, paste, select all, and find were not implemented. (Bug #52834, Bug #51806)
In the Variables tab of the Administrator, variables with long descriptions were not displayed correctly. They appeared wrapped to a new line, and clipped by the height of the Description row. (Bug #53025)
Each time an Admin tab was started an
cscript.exe was executed.
However, when the Admin tab was closed the
cscript.exe process was not
terminated. This resulted in ever increasing numbers of
cscript.exe processes, which consumed
resources unnecessarily, and constituted a resource leak.
In the Export to Disk tab of the Administrator's Data Dump facility, selecting multiple schemata for export to a self-contained file resulted in this exception:
unhandled exception: local variable 'tables' referenced before assignment.
If an SQL statement was selected in the SQL Statements area of the SQL Editor, and copied to the snippets list using the Save SQL to Snippets List toolbar button, then the statement was only partially saved, the beginning of the statement being missing. This only happened for lines after the first line. Also, the further down the copied statement was located, the less text was successfully copied to the snippets list. This resulted in statements further down the code being heavily truncated, with only the latter portion of the statement being saved. (Bug #51474)
If a snippet was deleted from the Snippets tab in the SQL Editor, after MySQL Workbench was restarted the deleted snippet would reappear as if it had never been deleted. (Bug #51335, Bug #52558)
SQL Editor syntax highlighting did not correctly recognize
escaping of the single quote character ('). Queries such as
SELECT '\'' FROM DUAL; were therefore not
If multiple SQL Editor tabs were opened, closing the last one caused MySQL Workbench to crash. (Bug #53061)
Selecting multiple tables at the same time in the Overview tab of the SQL Editor caused MySQL Workbench to crash. (Bug #52922)
On Windows, if SQL Editor was using a named pipe connection, and the SQL Editor tab was closed, MySQL Workbench stopped responding to user input and had to be killed using the Task Manager. (Bug #53021)
When switching between Model Overview Page, and EER Diagram View, MySQL Workbench incorrectly rendered the EER Diagram View inside the Table Editor panel. (Bug #52778)
The View Editor deleted text pasted into the editor by the user. This happened if, for example, a view was copied from the editor, a new view created and the copied text pasted into the new view. At this point the pasted text would be deleted by the auto-parsing facility of the View Editor. (Bug #52433)
In the Columns tab of the Table Editor, if a comment was added to a column, or a column with a comment was selected, then when another table was double-clicked to load it into the Table Editor, the comment for the column previously selected was still displayed in the inactive Comments area. (Bug #51495)
When using the Forward Engineer SQL Script wizard, if an existing script file was selected to be overwritten, the wizard would not continue, the file had to be deleted first. (Bug #46920)
If a schema was opened and an object editor, such as the Table Editor was opened, MySQL Workbench crashed if the schema was closed and immediately reopened. (Bug #53027)
When an EER Diagram was displayed, the Properties tab was empty. Also, if a table in the EER Diagram was selected, the Properties tab remained empty. (Bug #52971)
The MySQL Workbench make targets, with the exception of
make all, were broken by the file
The MySQL Workbench
script contained a construct incompatible with NetBSD. The
test == instead of
While MySQL Workbench was starting up, if the Windows screensaver activated, this led to unpredictable behavior of MySQL Workbench. For example, the application could freeze, fail to redraw its main window, or display artifacts. On other occasions the application was not able to accept keyboard input, and had to be terminated using the Task Manager. (Bug #52780)
In the results editor of the SQL Editor, deleting more than two hundred records resulted in this error:
Attempting to Read or Write protected memory. This is often an indication that other memory is corrupt
This happened when using either the delete key or the Delete Rows context-sensitive menu option. (Bug #52951)
If a table comment contained a single quote character, an error resulted when an attempt was made to synchronize this with a live server. This was because the code generated by the synchronization process did not escape single quotation marks in the table comments. (Bug #52608)
In the Reverse Engineer Database wizard, on the Connection Options page, if the first empty connection was selected from the Stored Connection list, and then the Connection Method changed, the fields on the Parameters tab did not change accordingly. (Bug #51742)
When selecting Print Preview for an EER Diagram, the objects in the preview appeared primarily as black filled rectangles. (Bug #51513)
In the Columns tab of the Table Editor, the bottom button of the comments scrollbar was situated too low, making downward scrolling very difficult because only part of the scrollbar button was exposed. (Bug #51496)
In the Reverse Engineer Database wizard, on the Select Schemata page, any schema name containing an underscore was displayed without the underscore character. Further, if the Alt key was pressed, the underscores appeared under the first character located after where the underscore should have been displayed, giving the character the appearance of being an accelerator key. (Bug #51141, Bug #52965)
MySQL Workbench crashed when the
located in the Server Access Management tab
of the Accounts facility in the Administrator, was clicked.
MySQL Workbench failed to compile from source due to a missing
#include <stdarg.h> statement in the
In the EER Diagram view, layer objects did not respond to edit commands (either double-clicking or using the Edit Layer context-sensitive menu option). (Bug #52822, Bug #52823)
In the Columns tab of the Table Editor, if a column was right-clicked on, and then Move Up selected, the column ordering was not updated within the Columns tab, until the area was clicked again. (Bug #51139)
When MySQL Workbench was sized to 1280 x 800, the Start Export button was not visible in the Export to Disk tab of the Data Dump facility. (Bug #52932)
When building MySQL Workbench, the build process failed if the
--no-copy-dt-needed-entries linker option was
specified (this happens by default when building on Fedora 13).
The HUD blocked access to other applications that were running. This was particularly a problem when Administrator or SQL Editor were launched from the Home screen, and took a long time to load. (Bug #53006)
The MySQL Workbench dependency on
has changed to use version 16 of the library rather than 15.
Print to PDF, Print to PS File, and all export functions did not work correctly. For example, if Print to PDF was selected, MySQL Workbench would attempt to open a new document, and if the user proceeded, the current document would be closed.
Further, selecting the menu option Save Model As resulted in the Open Document dialog being displayed. If the user clicked Yes the application became stuck in a loop, if No was clicked an error dialog was displayed. (Bug #52909)