[MDEV-10431] Please implement mysqldump --add-drop-trigger from MySQL 5.6 Created: 2016-07-25  Updated: 2017-05-04  Resolved: 2017-05-04

Status: Closed
Project: MariaDB Server
Component/s: Scripts & Clients
Fix Version/s: 10.2.6

Type: Task Priority: Major
Reporter: Phoenix the II Assignee: Oleksandr Byelkin
Resolution: Fixed Votes: 1
Labels: 10.2-ga

Sub-Tasks:
Key
 Summary
 Type
 Status
 Assignee
MDEV-12704 Document mysqldump --add-drop-trigger... Technical task Closed Ian Gilfillan  

 Description   

It's been implemented on MySQL 5.6.0:

See:

https://bugs.mysql.com/bug.php?id=34325

Needed for dumping and easier recreating triggers to another 'DEFINER'



 Comments   
Comment by Sergei Golubchik [ 2016-10-09 ]

Wouldn't it be simpler always to use CREATE OR REPLACE TRIGGER in mysqldump?

Comment by Elena Stepanova [ 2017-01-24 ]

If we want to do/fix it in 10.2, it should probably go before GA.
I don't think using CREATE OR REPLACE in mysqldump is a good idea, it will make it unusable for all MySQL and for MariaDB 5.5.

Comment by Oleksandr Byelkin [ 2017-05-03 ]

revision-id: 2761c2e4c1e3fcf95346fcabc6ae23f9e4afc326 (mariadb-10.2.5-129-g2761c2e4c1e)
parent(s): 52463ccff7ee5024f00541c12938ffbaf9b93958
committer: Oleksandr Byelkin
timestamp: 2017-05-03 12:26:57 +0200
message:

MDEV-10431: Please implement mysqldump --add-drop-trigger from MySQL 5.6

pot of mysql changeset by Georgi Kodinov <Georgi.Kodinov@Oracle.com>:

Bug #34325 : --add-drop-trigger option for mysqldump

Implemented the --add-drop-trigger option to prepend each
CREATE TRIGGER in the dump file with DROP TRIGGER.
The option is off by default. Added a test case.

—

Generated at Thu Feb 08 07:42:10 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.