couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Truemper <>
Subject Re: potential conflict resolution strategy
Date Fri, 13 Nov 2009 22:13:34 GMT

> assuming that this is a topology that we want to have for the time being,
> what are the group's thoughts on this resolution strategy:
> - in addition to storing the actual document, keep a record of which fields
> are being modified (call this copy a)
> - when a conflict is detected, retrieve couchdb's copy (call it copy b), and
> apply the changed fields 'only' from copy a, to copy b.
> - save copy b with the net difference.
I think you should really try to avoid doing this type of handling client side when you have
multiple clients with multiple caches. Looks like the source of many race conditions...

View raw message