-
Notifications
You must be signed in to change notification settings - Fork 59
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
Exclude DEFINER on Database Export #179
Comments
The WordPress schema is very primitive, it doesn't contain any stored procedures or similar. Therefore I think we should be safe by either stripping the I'd love for more feedback on this by database experts, though, as this can potentially be a risky proposition... |
I agree. I am not a db expert either so it would be great to have some other input on this. :) |
Hi, https://aws.amazon.com/premiumsupport/knowledge-center/definer-error-mysqldump/ |
For now, you should be able to use a work-around by stripping the offending line with
|
Feature Request
Describe your use case and the problem you are facing
When exporting databases, it is a common issue that sometimes the restoration cannot be completed due to this line (or similar:
/*!50013 DEFINER=
user@
%SQL SECURITY DEFINER */
When this happens, the import normally fails with error when trying to import it.
Some links with the issue (from 2010 one of them):
https://dbperf.wordpress.com/2010/04/12/removing-definer-from-mysql-dump/
https://stackoverflow.com/questions/9446783/remove-definer-clause-from-mysql-dumps
Describe the solution you'd like
I think that adding an option to exclude the DEFINER from the export or to remove it after the export automatically will improve the reliability of the export data.
Alternatively could be that the IMPORT ignore that line, but I think this is more an export issue than a import one.
Thanks!
The text was updated successfully, but these errors were encountered: