Changes in MySQL Workbench 5.2.4 (2009-10-07)

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

• Functionality Added or Changed

• Bugs Fixed

Functionality Added or Changed

• Some keyboard shortcuts have been changed.

  On Microsoft Windows and Linux Control+Y is now used for Redo. OS X continues to use Command+Shift+Z as its default for Redo. For Synchronize Model, Control+Alt+Y is used on Windows and Linux, and Command+Control+Y is used on OS X. (Bug #46285)

Bugs Fixed

• When editing a stored routine or trigger in the Table Editor, the cursor would relocate to the top of the editing window if a key was not pressed for a few seconds.

  Note

  On Windows this issue was fixed in 5.1.18. On OS X this issue was fixed in 5.2.4. On Linux this issue was fixed in 5.2.7.

  (Bug #48156)

• If a new empty EER diagram was created, then Model, Relationship Notation, Connect to Columns was selected, MySQL Workbench generated these messages:

  ** Message: item_activated: 0x28d5cf0 ->
  'plugin:wb.view.setRelationshipNotation:fromcolumn'
  ** Message: unhandled message 4: wb.view.setRelationshipNotation finished in 0.00s

  These messages were not generated if the EER diagram contained at least one table. (Bug #47565)

• When a model was synchronized, this incorrect SQL was generated:

  CREATE  TABLE IF NOT EXISTS `synthescom`.`adx_clienti` (
  
    `id` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT ,
  
    `citta` VARCHAR(100) NULL DEFAULT NULL ,
  
    `provincia` VARCHAR(100) NULL DEFAULT NULL ,
  
    PRIMARY KEY (`id`)
  
  ENGINE = MyISAM
  
  DEFAULT CHARACTER SET = utf8
  
  COLLATE = utf8_general_ci;

  Note that the closing parenthesis, which should have been located after the PRIMARY KEY statement, is missing. Thats resulted in this error being generated:

  ERROR: Error 1064: You have an error in your SQL syntax; check the
  manual that corresponds to your MySQL server version for the right
  syntax to use near 'ENGINE = MyISAM
  
  DEFAULT CHARACTER SET = utf8
  
  COLLATE = utf8_general_ci' at line 13

  (Bug #47407)

• When a table was opened for editing in the Query Editor, the DECIMAL column values appeared in the result set as integer values, disregarding precision and scale settings. The fractional part of the number was discarded. It was also not possible to add the fractional part of the number during editing. (Bug #47405)

• In the EER Diagram, Layer names were not rendered. This only happened with OpenGL rendering (only on Microsoft Windows). (Bug #47385)

• When the Query Database menu option was selected, the explorer on the right-hand side displayed Tables, Views and Routines, but when the Routines folder was expanded the routines contained in the model were missing. (Bug #47088)

• Clicking the Test Connection button in DB Connection Editor wizard did not appear to have any effect. (Bug #47083)

• In the Query Editor, when an attempt was made to expand a schema and select a table, this exception was generated:

  ************** Exception Text **************
  System.AccessViolationException: Attempted to read or write protected memory. This is
  often an indication that other memory is corrupt.
     at MySQL.Grt.TreeModel.expand_node(NodeId node)
     at MySQL.Grt.GrtTreeModel.TreeViewExpanding(Object sender, TreeViewAdvEventArgs e)
     at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
     at Aga.Controls.Tree.TreeViewAdv.OnExpanding(TreeNodeAdv node)
     at Aga.Controls.Tree.TreeViewAdv.SetIsExpanded(TreeNodeAdv node, Boolean value)
     at Aga.Controls.Tree.TreeViewAdv.SetIsExpanded(ExpandArgs eargs)
     at Aga.Controls.Tree.TreeViewAdv.SetIsExpanded(TreeNodeAdv node, Boolean value, Boolean
  ignoreChildren)
  ...

  (Bug #47044)

• On OS X using cmd + backspace to delete a column in the table editor did not work. (Bug #46613)

• In the Synchronize Model with Database dialog the text in the upper right area of the dialog did not wrap correctly, resulting in some text not being visible. (Bug #45455)

• MySQL Workbench EER Diagram view did not permit the creation of a foreign key constraint on a primary key. (Bug #39546)