Bug #39119 Missing DROP TRIGGER commands on export

Description:
Situation: export table with triggers
Case
- export table + triggers with "generate DROP TABLES statements" checked -> DROP TRIGGER IF EXISTS appears in the sql export

- export table + triggers with "generate DROP TABLES statements" unchecked -> DROP TRIGGER IF EXISTS does NOT appear in the sql export

- export triggers with "generate DROP TABLES statements" checked -> DROP TRIGGER IF EXISTS does NOT appear in the sql export

- export triggers with "generate DROP TABLES statements" unchecked -> DROP TRIGGER IF EXISTS does NOT appear in the sql export

How to repeat:
- export table + triggers with "generate DROP TABLES statements" checked -> DROP TRIGGER IF EXISTS appears in the sql export

- export table + triggers with "generate DROP TABLES statements" unchecked -> DROP TRIGGER IF EXISTS does NOT appear in the sql export

- export triggers with "generate DROP TABLES statements" checked -> DROP TRIGGER IF EXISTS does NOT appear in the sql export

- export triggers with "generate DROP TABLES statements" unchecked -> DROP TRIGGER IF EXISTS does NOT appear in the sql export

Thank you for a problem report. Verified just as described.

In my test incorrect trigger name was used even when DROP TRIGGER statement was generated:

DROP TRIGGER IF EXISTS `mydb`.`SYNTAX_ERROR_1` //
create trigger trg before insert into table1 for each row set @a:=1;//

Fixed in revs 3195 and 3196

The option for generation of the DROP statements has been changed too to indicate it is not only for tables.

Fixed as described by developer. fix will go into 5.0.25

An entry was added to the 5.0.25 changelog:

When triggers were exported with the Generate DROP TABLES statements option checked, DROP TRIGGER IF EXISTS did not appear in the exported SQL.