Bug #9160 mysqldump doesn't save triggers
Submitted: 14 Mar 2005 10:27 Modified: 14 Mar 2005 10:35
Reporter: Gleb Paharenko Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.3 OS:Linux (Linux)
Assigned to: CPU Architecture:Any

[14 Mar 2005 10:27] Gleb Paharenko 
Description:
mysqldump doesn't stores triggers in the dump file. Also I didn't find SQL statement
to see what triggers in my database.

How to repeat:
create trigger and dump the database with mysqldump, you'll not see triggers in the dumpfiles

Suggested fix:
Add something like SHOW TRIGGERS and SHOW CREATE TRIGGER, and
give to mysqldump ability to save triggers definitions in the dump files
[14 Mar 2005 10:35] MySQL Verification Team 
This is related too to bug: http://bugs.mysql.com/bug.php?id=9056