-
Notifications
You must be signed in to change notification settings - Fork 65
Description
Feature Request
- [x ] Yes, I reviewed the contribution guidelines.
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!