Move specific DB tables (supporting wildcard names)

[alessandro-fazzi]

Hello,

now that we have slowly moved along the way and we have declared wp-cli as a dependency, we have possibility to afford this feature in a secure, standard way.

I'm thinking about solving 2 different problems here:

1. dump only tables with specific prefix
2. dump only certain tables

The config inside movefile.yml would look like

database:
  name: 'mydb'
  password: 'mypwd'
  [...]
  tables:
    - 'wp_posts'
    - 'wp_users'

or

database:
  name: 'mydb'
  password: 'mypwd'
  [...]
  tables:
    - 'wp_*'

or a mix

database:
  name: 'mydb'
  password: 'mypwd'
  [...]
  tables:
    - 'custom_prefix_*'
    - 'wp_posts'

The implementation would rely on wp db tables command; slow (wp-cli is slow to load) but rock solid. I'd cycle over the array of strings tables and construct a string from the output of

wp db tables 'custom_prefix_*' --all-tables

intercepting the use of the wildcard and passing thus to wp-cli; or simply appending 'wp_posts' because no wildcard is used.

The resulting mysqldump command would be, e.g.:

mysqldump --host=localhost --user=root --result-file="/Users/fuzzy/dev/sshwordmove/wp-content/dump.sql" --default-character-set=utf8 sshwordmove wp_posts custom_prefix_table1 custom_prefix_table2

---

Tables would be specified for each environment (local and/or remote) based on the desired behaviour. Opening to scenarios where I can pull only wp_posts from production, but wp_users and wp_posts from staging.

---

Note:

• import command would not be altered, since it will import whatever was previously exported.
• blocked by Disjoin backup methods from dump methods in WpcliSqlAdapter #467
• should be extended by Pulling instead of Pushing database #482

[alessandro-fazzi]

This feature embraces different previously discussed features such as #442 #219 and a request reported inside #432 (but was a bit OT there)

[taliesinpenbardd]

Following your last answer on #442 (and to follow this thread 😃) : yet simpler if --all-tables-with-prefix doesn't need help to get the db prefix.

[alessandro-fazzi]

Yep, simpler, but less powerful: if I'd be developing a plugin with a prefix like wpprefix_customprefix_teble it could be useful to customise the prefix. It could be over-engineered, but I'd like to find a feature which could rule them all.

[ThomasGHenry]

Happy Issue Anniversary! Did this happen?

[alessandro-fazzi]

I can't assure when the feature will be implemented (it also has a blocker), but I can assure that when it will this issue will be updated.

[MarkErik]

If I am reading this correctly, it would allow to exclude the users from a DB push / pull operation?
This would be a fantastic feature.

[alessandro-fazzi]

If I am reading this correctly, it would allow to exclude the users from a DB push / pull operation?
This would be a fantastic feature.

Hey @MarkErik the feature is a different one actually.

But the one you’re talking about already exists; please search for “forbid” in the documentation 😉

[MarkErik]

Dear @pioneerskies, my apologies, I might not have clearly commented what I was hoping for and perhaps for missing something in the documentation.

In my comment: "exclude the users from a DB push / pull operation" what I was hoping to say was that the registered WordPress users could be excluded from Push / Pull operations.

I had also opened a feature request expanding on this so that pages / posts / users etc could be selectively excluded from push / pull operations.

Note, I had tried the forbid command:
forbid:
push:
db: true

And as a test I registered a new WordPress user, and created a page locally, and as expected when I pushed, neither showed up on the production site.

My goal is that I can create new pages (perhaps with new plugins) locally and push them to the production server, and in most situations for safety prevent the accidental deletion of elements that I am not working with.

[alessandro-fazzi]

In my comment: "exclude the users from a DB push / pull operation" what I was hoping to say was that the registered WordPress users could be excluded from Push / Pull operations.

@MarkErik you could try to exclude your wp_users table through mysqldump_options config. That won't consider consider user-related options which are on another table, but you'd accomplish to not pull/push registered users.

[MarkErik]

@pioneerskies Thank you for that suggestion, I will give it a try. Feel free to remove my earlier comments if you'd like to keep the original feature discussion cleaner :)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.