On Wed, Jan 28, 2009 at 02:19:27PM -0500, Damien Katz wrote: > There is no generalized conflict resolution algorithm possible for > distributed edits. But for certain types of uses, as you note, it can be > automated. > > For things that can't be automated, you can track diffs in the app for > later inspection. For each new revision, diff the changes with the > previous and attach the diff, or put the diffs into into another json > field.
It seems like the ideal place to put this app logic would be inside the database itself - can validate_doc_update also modify the data being stored? Otherwise all the clients must contain the same diff logic and must remember to apply it every time they make an update. > It's already planned to having integrity hashes in documents and > attachments. It's not that hard, just hasn't been done yet. Is this planned to use this for _rev too? If so, independent updates which make exactly the same change would be automatically non-conflicting. Regards, Brian.
