Help get this topic noticed by sharing it on Twitter, Facebook, or email.

Opposite functionality of 'TablesToSkip'

I am curious about the current solution for skipping tables for refresh all and replicate all. In our use case, it would be much more appropriate to only list the tables we want to replicate and refresh rather than listing the tables to skip. As our implementation team builds out new features and installs new plugins, we don't automatically want to sync these new tables. To avoid this, we would need to setup a job to query for any new tables and add those to the 'TablesToSkip' table.

Is it a more common use case to have the current implementation and if so, it might be a nice feature to be able to swap this by configuration.
1 person likes
this idea