Bug #49313 MySQL Workbench data modeling detects table rename but fails to generate code
Submitted: 1 Dec 2009 23:36 Modified: 18 Jan 2010 11:46
Reporter: Giuseppe Maxia Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.2.10,5.1.18 OS:MacOS
Assigned to: Alexander Musienko CPU Architecture:Any
Tags: modeling, rename, synchronize, workbench

[1 Dec 2009 23:36] Giuseppe Maxia
Description:
If you rename a table using the WB data modeling, and then ask to synchronize to its source, WB detects the change, but does not generate any code to update the source.

How to repeat:
1. reverse engineer the Sakila database
2. rename film_text to film_text1
3. generate the schema diff report (the change is detected)
4. start the "synchronize database" feature
5. look at the "model and database difference". The change is detected
6. go on to "preview database changes to be applied". No DDL statement is created.

Suggested fix:
Generate a renaming statement for the changed object.
[15 Jan 2010 18:42] Johannes Taxacher
fix confirmed. will be included in 5.2.12
[18 Jan 2010 11:46] Tony Bedford
An entry has been added to the 5.2.12 changelog:

If a database was reversed engineered from a source, and a table renamed, then although this change was detected by MySQL Workbench, no DDL code was generated if an attempt was then made to synchronize this change with the source.