MySQL Bugs: #54426: Export to Backup Project folder export triggers twice

Bug #54426	Export to Backup Project folder export triggers twice
Submitted:	11 Jun 2010 11:32	Modified:	29 Jun 2010 10:34
Reporter:	Csaba Bukor	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	5.2.22	OS:	Any (Windows XP SP3, Mac OS X)
Assigned to:	Alexander Musienko	CPU Architecture:	Any

Description:
The Export to Backup Project folder option exports the triggers in the table files and int the routines also. So if you try to import it it cause an error message.

How to repeat:
Export a schema which contains triggers with Export to Backup Project folder and Dump Stored routines option. Import the exported folder and it stops with a trigger error, because the table and the routine files also contains the same trigger.

Thank you for the bug report. Verified just as described on Mac OS X:

valeriy-kravchuks-macbook-pro:5.1 openxs$ grep -ni trigger ~/dumps/Dump20100611/*
/Users/openxs/dumps/Dump20100611/test_routines.sql:28:/*!50003 CREATE*/ /*!50017 DEFINER=`root`@`localhost`*/ /*!50003 trigger ti before insert on tt for each row set new.c1 = 1 */;;
/Users/openxs/dumps/Dump20100611/test_tt.sql:52:/*!50003 CREATE*/ /*!50017 DEFINER=`root`@`localhost`*/ /*!50003 trigger ti before insert on tt for each row set new.c1 = 1 */;;

Fix confirmed in repository.

An entry has been added to the 5.2.25 changelog:

In the Data Dump section of the Administrator, using the Export to Backup Project Folder option resulted in the triggers being exported to both the table files and the routines files. If an attempt was then made to import the exported files, an error resulted due to the duplicated triggers.