-
Notifications
You must be signed in to change notification settings - Fork 45
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
Problems with Views - "ERROR 1449 ... The user specified as a definer ('xxx'@'xxx') does not exist" #109
Comments
I think it makes sense to be able to skip views for certain commands. However, the default behavior for I suggest the following changes (in 2 separate PRs with corresponding tests for each):
Do you think this makes sense? |
Sorry for the slow response. That sounds sensible - I'll aim to get on with this at #wcldn today. I'll try and remember to also check if db export includes views, as that's a other place a --skip-views might make sense. |
This is a suggest / query / pre-PR question.
I am pulling a db from serverA to serverB and running a search-replace on it. It is failing because the dB contains a view. The view references the serverA MySQL user which doesn't exist on serverB.
(presuming I'm not missing something / haven't messed something up in my setup...)
I don't know of any reason to run a search-replace on a View as they are dynamic by nature. Would a PR to skip them be accepted? Is there any reason Views should be included?
These would work on MySQL/MariaDB (but haven't been extensively tested):
It would mean modifying
wp_get_table_names()
in wp-cli/php/utils-wp.php fairly extensively, unless there's an easier way to identify Views.I think this is going to get more widely applicable if the use of a View in core goes ahead (wasn't there talk of a View for taxonomy data?)
While I'm obviously talking about modifying a function in core wp-cli I thought I'd post this hear first as the most obvious (to me) place that it would affect and use case for the change.
The text was updated successfully, but these errors were encountered: