-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Database backup doesn't include triggers #9036 #11369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ADDED getTableTriggersSql() and now it returns valid SQL with drop & create queries for triggers
Shouldn't they be recreated with |
@orlangur I think that this issue is not about indexer triggers but SQL database triggers. If you create inside SQL database custom trigger than, before my fix, those wouldn't be dumped to a backup file (you could't recreate them from backup) |
I don't think making any changes to database, like adding triggers, manually is a Magento way. Why not simply implement it in |
@orlangur I know that this isn't Magento way to do something, but I didn't report this issue nor I've put it on to-do list on SQUASHTOBERFEST :) |
@hostep I read it before my very first comment here :) Just that I don't think such case is valid. Does Magento backup database tables created manually? It is fine to dump triggers when you do it with some tooling. From within Magento I don't think it's a good idea to dump anything not application-specific. Let me raise this question in maintainers group, maybe I'm missing something. |
ADDED getTableTriggersSql() and now it returns valid SQL with drop & create queries for triggers
Fixed Issues (if relevant)