incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jens Alfke <j...@couchbase.com>
Subject Re: conflict determination not by fields
Date Tue, 30 Aug 2011 05:51:28 GMT

On Aug 29, 2011, at 10:35 PM, gaoyong pan wrote:

if two changes are not on the same field, then there will be no conflict happening actually.

That’s not true. It depends on the schema. It won’t work...
- If one field is a checksum [or digital signature] of other fields
- If two fields are mutually exclusive (you can have field A or field B but never both)
- If one edit deletes a field while the other edit modifies it
- etc.

If the documents in _your_ app can be merged that way, then write a simple function to merge
them that way to resolve conflicts. Problem solved. But CouchDB isn’t going to do it automatically
because in some cases it will cause mangled documents.

—Jens

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message