Re:How the Dropbox Datastore API Handles Conflicts – Part Two
by pkj on Saturday August 31, 2013 @07:03AM
(#6306494)
If a client app is processing the cust record, how would cust.email look like ? Typically I would assume a single value, but in case of unresolved conflicts will it be a iterator/array ?
Re:How the Dropbox Datastore API Handles Conflicts – Part Two
by jchrisa on Saturday August 31, 2013 @09:38AM
(#6306796)
The client will have N copies of the customer record, so the record schema doesn't change. Instead all the potentially valid versions of it are preserved until a peer (any client or server) marks the conflict as resolved.
Re:How the Dropbox Datastore API Handles Conflicts – Part Two
by erikb on Thursday September 05, 2013 @05:36PM
(#6337232)
this is not necessarily the number one rule. There are other rules as well, e.g. being 100% consistent, fast or available. I'm not a database expert but I don't think you can have it all.
For instance on a customer record you might have three sales folks all qualify a lead as a 4, one adds a fax number, one adds an email address, and one adds the same fax but a different email, and a note about the best time to call. If the database forced the application to merge on encountering each update, there'd never be a chance to set all three versions side by side and make an informed comparison. Instead it would be luck that A and B merge, and then the result merges with C. Or some other order.
Where it gets really useful is if you have different actors that have ownership of the merge on different fields. So for instance you could partially resolve the conflict by merging some fields automatically but present a human with the full set of options for a bigger octopus merge on, say, the notes field.