We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
More info: https://aws.amazon.com/premiumsupport/knowledge-center/definer-error-mysqldump/
We tried to set the log_bin_trust_function_creators parameter to true as suggested in the article, but it didn't fix the issue.
log_bin_trust_function_creators parameter
true
Idea for a workaround: dump whole database w/o triggers, then dump only triggers, process the first dump, at the end concatenate both.
Known issue: If some environment ignores a table with trigger, the error might occur during dump import.
The text was updated successfully, but these errors were encountered:
#61: Workaround for AWS RDS not allowing creating triggers
962fbf7
Merge pull request #64 from swiftotter/56-table-ref-issues
02ec778
#56 & #61 - Dump refactored
michalbiarda
No branches or pull requests
More info: https://aws.amazon.com/premiumsupport/knowledge-center/definer-error-mysqldump/
We tried to set the
log_bin_trust_function_creators parameter
totrue
as suggested in the article, but it didn't fix the issue.Idea for a workaround: dump whole database w/o triggers, then dump only triggers, process the first dump, at the end concatenate both.
Known issue: If some environment ignores a table with trigger, the error might occur during dump import.
The text was updated successfully, but these errors were encountered: