- A.3 Changes in Release 5.0
- A.3.1 Changes in MySQL Workbench 5.0.30 (18th February 2009)
- A.3.2 Changes in MySQL Workbench 5.0.29 (12th December 2008)
- A.3.3 Changes in MySQL Workbench 5.0.28 (6th December 2008)
- A.3.4 Changes in MySQL Workbench 5.0.27 (7th November 2008)
- A.3.5 Changes in MySQL Workbench 5.0.26 (16th October 2008)
- A.3.6 Changes in MySQL Workbench 5.0.25 (12th September 2008)
- A.3.7 Changes in MySQL Workbench 5.0.24 (12th August 2008)
- A.3.8 Changes in MySQL Workbench 5.0.23 (25th June 2008)
- A.3.9 Changes in MySQL Workbench 5.0.22 (27th May 2008)
- A.3.10 Changes in MySQL Workbench 5.0.21 (27th April 2008)
- A.3.11 Changes in MySQL Workbench 5.0.20 (26th April 2008)
- A.3.12 Changes in MySQL Workbench 5.0.19 (15th April 2008)
- A.3.13 Changes in MySQL Workbench 5.0.18rc (not released)
- A.3.14 Changes in MySQL Workbench 5.0.17rc (07th April 2008)
- A.3.15 Changes in MySQL Workbench 5.0.16rc (26th March 2008)
- A.3.16 Changes in MySQL Workbench 5.0.15rc (17th March 2008)
- A.3.17 Changes in MySQL Workbench 5.0.14abeta (28th February 2008)
- A.3.18 Changes in MySQL Workbench 5.0.14beta (25th February 2008)
This section documents all changes and bug fixes that have been applied since the release of 5.0.25.
Bugs fixed:
When attempting to export a model using the File, Export, Forward Engineer SQL CREATE Script menu item, Workbench crashed on clicking the wizard's Finish button. (Bug#39578)
The Copy Insert to Clipboard action generated SQL with lower case keywords. This was not consistent with the behavior of the Copy SQL to Clipboard action. (Bug#39477)
Renaming a table and then selecting Forward Engineer SQL ALTER Script did not result in a
RENAMEstatement. Instead,DROPandCREATEstatements were generated. (Bug#39256)The script generated by the Export, Forward Engineer SQL CREATE Script menu item contained invalid statements when using two schemata. (Bug#39211)
Exported SQL code containing a trigger that called a procedure would fail when an
INSERTactivated the trigger. (Bug#39088)
