When deltas were detected, give option to review. ie:
2017-11-08 10:48:14 target encoding UTF8
2017-11-08 10:48:14 finding deltas..
2017-11-08 10:48:14
2017-11-08 10:48:14 |--------------------------------|Data Changes|--------------------------------|
2017-11-08 10:48:14 The following columns will be updated on local
2017-11-08 10:48:14 -updatedAt
2017-11-08 10:48:14 -operators_review_guests_view
2017-11-08 10:48:14 |------------------------------------------------------------------------------|
2017-11-08 10:48:14
2017-11-08 10:48:14 backing up target row..
2017-11-08 10:48:14 backup file can be found at /tmp/client-pool-skydiveabeltasman-wip-1510138092009.backup on this machine
2017-11-08 10:48:14 dumping update sql to disk..
2017-11-08 10:48:14 update sql is available for inspection at /tmp/client-pool-skydiveabeltasman-wip-1510138092009.sql on this machine
2017-11-08 10:48:14 Row has been cloned successfully..
2017-11-08 10:48:14 Type 'r' to (r)estore from backup, anything else to exit
could have an option like how when apt detects changes
Configuration file '/etc/foo/foo.conf'
==> Modified (by you or by a script) since installation.
Version in package is the same as at last installation.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** foo.conf (Y/I/N/O/D/Z) [default=N] ?
where the default is obviously(?) to accept incoming changes. But it would be hella nice to be able to see what the deltas are...
Wishlist item #493234554 after weight'n'balance and database normalisation (one guest, many clients)
When deltas were detected, give option to review. ie:
could have an option like how when apt detects changes
where the default is obviously(?) to accept incoming changes. But it would be hella nice to be able to see what the deltas are...
Wishlist item #493234554 after weight'n'balance and database normalisation (one guest, many clients)