MySQL Bugs: #39989: Renaming triggers cause failed database synchronisation

Bug #39989	Renaming triggers cause failed database synchronisation
Submitted:	12 Oct 2008 15:22	Modified:	11 Nov 2008 11:25
Reporter:	Robert Armour	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.0.25 Rev 3427	OS:	Windows (XP SP2)
Assigned to:	Alexander Musienko	CPU Architecture:	Any
Tags:	Triggers workbench synch

Description:
If a trigger is renamed, and the design synched with a database instance, the generated DDL creates a trigger with the new names and then drops the trigger with the old name.

This results in the following error...

Error 1235: This version of MySQL doesn't yet support 'multiple triggers with the same action time and event for one table'

...which can be worked around by going back a step in the wizard and then forward again. (It works the second time because the original trigger has now been dropped, removing the reason for the error)

How to repeat:
Forward engineer a database design, that contains a trigger, to a schema instance.
Rename a trigger and then synchronize woth the same schema instance.

Suggested fix:

Generate the synchronisation script so that the DROP takes place before the CREATE.

Thank you for the bug report.

this is fixed and will be incorporated in 5.0.27

An entry was added to the 5.0.27 changelog:

If a trigger was renamed, and the design then synched with a database instance, the generated SQL created a trigger with the new name and then dropped the trigger with the old name. This resulted in the following error: 

Error 1235: This version of MySQL doesn't yet support 
'multiple triggers with the same action time and event for one table'