When working with multiple people, and several environments, there will be problems with data parity between environments. My development environment usually is lagging behind content wise from the staging site that others use to work their content on, and I frequently use WP DB Migrate Pro to pull the changes to my own environment.
However, as it's "dumb", it overwrites my current database without preserving anything. It can be configured to only pull certain tables, but since ACF fields nowadays live in the wp_posts table, we might end up overwriting new field groups by accident.
If this plugin could check the staging site for changes (just check if the database has updated since last push), these kind of accidents could be avoided.
When working with multiple people, and several environments, there will be problems with data parity between environments. My development environment usually is lagging behind content wise from the staging site that others use to work their content on, and I frequently use WP DB Migrate Pro to pull the changes to my own environment.
However, as it's "dumb", it overwrites my current database without preserving anything. It can be configured to only pull certain tables, but since ACF fields nowadays live in the wp_posts table, we might end up overwriting new field groups by accident.
If this plugin could check the staging site for changes (just check if the database has updated since last push), these kind of accidents could be avoided.