Changes in MySQL Workbench 5.2.22 (2010-06-02)

This section documents all changes and bug fixes applied since the release of MySQL Workbench 5.2.21.

• Functionality Added or Changed

• Bugs Fixed

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 now does not automatically add a .sql extension on Linux. However, on Windows, the file extension is added if one is not specified. (Bug #53731)

• MySQL Workbench now indicates that changes need to be saved using only an asterisk in the Model Overview tab, rather than this being reflected on individual EER Diagrams. (Bug #53042)

• The SQL Editor now includes a new Set as Default Schema context menu item. 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 list located at the top of the Object Browser. (Bug #51479)

• MySQL Workbench now supports creating a new tab in tabbed interfaces by using Control+T on Windows and Command+T on OS X. (Bug #48798)

• 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 was clicked, or a new tab was clicked before the cursor was moved away from the value being changed, the change was silently reverted. (Bug #54060)

• If the Manage Server Instances dialog was launched, and either the New or Delete button was clicked, and then the dialog was closed, MySQL Workbench crashed if the New Server Instance action item was then clicked on the Home screen. (Bug #54028)

• The Gnome keyring package was a dependency of MySQL Workbench. It was undesirable to require its installation on KDE-based systems. (Bug #54010)

• MySQL Workbench did not size its application window correctly on screen sizes with a 16/9 aspect ratio. (Bug #53984, Bug #11761483)

• 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 because 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, it would then change back to its original setting. (Bug #53946)

• In the EER Diagram view, heavy flicker resulted if the cursor was hovered over relationship lines or tables. (Bug #53941)

• When a table containing triggers was loaded into the Alter Table dialog of SQL Editor, clicking 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.

  Because 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 now includes a new global option that 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 this 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, deleting a snippet from the snippet list using the toolbar button caused the first snippet to be 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 entered into the SQL Query tab, and then the application exited, MySQL Workbench did not prompt the user regarding unsaved changes, so they were lost. (Bug #53848)

• In the SQL Editor, when renaming views or routines using the live editor, the generated ALTER script contained only DROP statements and not CREATE statements. (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 this 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 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 problem happened if the line preceding the second DROP statement was terminated with a space. (Bug #53760)

• With multiple tabs open in the SQL Editor, 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, 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, automatic data type completion did not occur if the type was entered in lowercase. MySQL Workbench now completes the data type regardless of lettercase. (Bug #53710)

• Compiling MySQL Workbench from source failed with these 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 entered in the SQL Query tab, and then Command+Enter was 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 list 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, this error occurred when an export was generated:

  mysqldump: Error 2020: Got packet bigger than 'max_allowed_packet' bytes when dumping
  table 'xxx' at row: 1

  This happened only 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 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 the Model, Create Diagram from Catalog Objects menu item. (Bug #53454)

• It was not possible to edit schema properties in the schema editor, such as name and default collation. (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)

• Loading a large script was loaded into the SQL Editor resulted in an out of memory exception. Memory exhaustion was caused by inefficient end of line conversion. The SQL Editor now supports custom end of line formats and preserves the original line endings used in the file. End of line conversion is no longer used and large files load faster and more efficiently. (Bug #53190)

• In the Manage DB Connections dialog, selecting 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, entering a column comment in the Comments tab and applying the changes did not save the comment. (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, 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 for print 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 an SQL file saved in 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, host names that contained a '-' character were sometimes not displayed correctly. (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)

• Attempts to forward engineer a project that contained a view failed with this 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 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 enable visibility of the full names. 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 if it was. The MySQL Server concerned was running on 64-bit Windows 7. (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 pressing Control+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)

• If a Workbench model file was double-clicked, MySQL Workbench crashed on launch. However, if MySQL Workbench was started using its application icon, and then the same model file was loaded from within MySQL Workbench, no problems were encountered. (Bug #49941)

• When using Create EER Model from SQL Script from the Home screen, the specified engine type was not present in the resulting EER model. (Bug #49568)