workbench-en.a4

MySQL Workbench Change History
• Pressing Ctrl-Z to undo the last change in an SQL Script text box deleted the entire script. (Bug#35649)
• Workbench is unable to read files such as Workbench Model Files from a non-English directory. (Bug#35547)
• Workbench allowed table comments to be entered longer than the maximum length of 60 characters. (Bug#34507)
• A crash could occur during foreign key creation. (Bug#33545)
• Autoplacing for display of complex schemas has been improved. (Bug#32888)
• Typing q in the GRT Shell caused a crash. (Bug#32755)
A.2.14. Changes in MySQL Workbench 5.0.17rc (07 April 2008)
This section documents all changes and bug fixes that have been applied since the release of 5.0.16rc.
Bugs fixed:
• Creating a new view and then deleting it caused a System.AccessViolationException. (Bug#35840)
• Editing a stored procedure within Workbench could cause an exception. (Bug#35828)
• The modified timestamp for an existing model was not correctly updated for all changes. (Bug#35719)
• Identifiers for field names in DML SQL statements would not be quoted correctly, allowing for reserved words to be included
in the SQL statements. (Bug#35710)
• Workbench would crash repeatedly when drawing the diagram for a table where the referenced column in a foreign key relationship
was blank. (Bug#35677)
• Identifiers using uppercase characters for stored procedures would automatically be modified to lowercase. (Bug#35650)
• When working with the SQL SCRIPT editor, it was not possible to select all the text in the display when using Ctrl A.
(Bug#35646)
• The MODEL NAVIGATION window could not be collapsed like other palettes. (Bug#35642)
• Modifying the primary key index definition for within the table view would not update the entity relationship diagram.
(Bug#35639)
• When validating an existing model using the Forward Engineer Wizard, MySQL-specific validation would fail. (Bug#35604)
• Deleting an existing layer on a diagram and then editing other objects on the same canvas could generate a number of exceptions,
and could corrupt the Workbench file. (Bug#35603)
• Switching to the Connect to Columns notation with an existing model would cause an exception. (Bug#35601)
• Data in BLOG and TEXT columns defined using the INSERTS tab would not be quoted correctly in the resulting SQL.
(Bug#35525)
• Opening an existing Workbench model with an invalid foreign key definition would cause an exception. (Bug#35501)
• Moving multiple tables on the same diagram, and then using Undo to revert the model to the original layout, only the first table
selected be returned to its original position. (Bug#35465)
• When adding a foreign key relationship within a catalog with an existing entity relationship diagram, the foreign key relationship
is not added to the existing diagram. (Bug#35429)
• The precise position of individual connections would not be retained when the schema was saved. (Bug#35397)
• Opening a GRT shell while the table editor is open would raise an exception. (Bug#35349)
• When modifying an existing foreign key relationship, the generated ALTER script did not reflect the modification. (Bug#35265,
Bug#35830)
• When creating foreign key relationships that point to more than one table, the same foreign key identifier for the same table
could be created. This would create invalid SQL code for creating the table. (Bug#35262)
• When importing an existing DB Designer schema, Workbench could crash. (Bug#35123)
92