MySQL Bugs: #39256: table rename not reflected in SQL ALTER Script

Bug #39256	table rename not reflected in SQL ALTER Script
Submitted:	4 Sep 2008 19:59	Modified:	13 Oct 2008 14:23
Reporter:	Exception e	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.0.24	OS:	Windows
Assigned to:	Alexander Musienko	CPU Architecture:	Any

Description:
In workbench 5.0.24 it is possible to rename tables. forward engineering to an  alter script doesn't result in a RENAME clause however. Instead a DROP and a CREATE statement is generated.

In workbench 5.0.23 this problem did *NOT* exist. However, changes to columns of a renamed table results in a DROP COLUMN and ADD COLUMN instead of CHANGE COLUMN.

How to repeat:
DO:
rename a table (can be via catalog or table editor)
choose File » Export » Forward Engineer SQL ALTER Script

EXPECT:
Someting like  ALTER TABLE mydb.t(...) RENAME TO mydb.t_renamed

ACUTAL RESULT:
workbench doesn't see that t is related to t_renamed, so you see something like
DROP TABLE table t;
CREATE TABLE t_renamed (...)

Thank you for the bug report.

Errors in comparison code have been corrected.
Bug will be fixed in 5.0.26

An entry was added to the 5.0.26 changelog:

Renaming a table and then selecting Forward Engineer SQL ALTER Script did not result in a RENAME statement. Instead, DROP and CREATE statements were generated.