You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually wp cli commands are limited in scope to the db prefix of the current installation, unless using e.g. --all-tables flag (e.g. in wp search-replace)
I suggest to also limit wp db reset (and perhaps also the other wp db commands) to the current page prefix (unless --all-tables is specified), as it will happen that people use wp db reset and, without realizing, delete ALL tables in the current database, instead of only the tables of the current installation.
The text was updated successfully, but these errors were encountered:
Usually wp cli commands are limited in scope to the db prefix of the current installation, unless using e.g. --all-tables flag (e.g. in wp search-replace)
I suggest to also limit wp db reset (and perhaps also the other wp db commands) to the current page prefix (unless --all-tables is specified), as it will happen that people use wp db reset and, without realizing, delete ALL tables in the current database, instead of only the tables of the current installation.
The text was updated successfully, but these errors were encountered: