mirror of
https://github.com/DBDiff/DBDiff.git
synced 2026-04-25 05:15:49 +03:00
[GH-ISSUE #47] Add support for triggers #172
Labels
No labels
bug
enhancement
good first issue
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/DBDiff#172
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @joogoo on GitHub (May 7, 2017).
Original GitHub issue: https://github.com/DBDiff/DBDiff/issues/47
Hi, this tool is great !
It's would be nice if it was also possible to have migration exports of triggers !
@jasdeepkhalsa commented on GitHub (Nov 24, 2017):
Hey @joogoo thanks for the suggestion.
So each time you, for example, add a trigger you want it to form part of the migration diff right?
I think this could be a feature which can be turned on, by default would be off, and would just run the MySQL command
show triggers;and then compare which triggers are in the source vs. the target, andCREATE TRIGGERthe ones the target database doesn't have andDELETE TRIGGERany that the target has which are not in the source, andUPDATE TRIGGERany which exist in both databases under the sametrigger_namebut their values differ somehow@nowarzz commented on GitHub (Dec 7, 2017):
and also procedures
@amit11111 commented on GitHub (Aug 7, 2019):
Hello,
Can you please let me know how to turn on for trigger migration.Currently I am not able to get trigger and procedure data into my .sql file which is generated by our tool.
Thank In Advance
Amit Kagadiya