Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D32EB8207 for ; Tue, 30 Aug 2011 05:52:16 +0000 (UTC) Received: (qmail 6702 invoked by uid 500); 30 Aug 2011 05:52:14 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 6294 invoked by uid 500); 30 Aug 2011 05:52:04 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 6280 invoked by uid 99); 30 Aug 2011 05:52:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Aug 2011 05:52:00 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jens@couchbase.com designates 206.225.164.30 as permitted sender) Received: from [206.225.164.30] (HELO EXHUB020-3.exch020.serverdata.net) (206.225.164.30) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Aug 2011 05:51:51 +0000 Received: from EXVMBX020-1.exch020.serverdata.net ([169.254.4.169]) by EXHUB020-3.exch020.serverdata.net ([206.225.164.30]) with mapi; Mon, 29 Aug 2011 22:51:28 -0700 From: Jens Alfke To: "user@couchdb.apache.org" Date: Mon, 29 Aug 2011 22:51:28 -0700 Subject: Re: conflict determination not by fields Thread-Topic: conflict determination not by fields Thread-Index: Acxm2Nx4upd3qZx0RxGUyFjmucKnfg== Message-ID: References: <44FBDC4C-26E3-4935-915F-EE0BA94267EC@couchbase.com> <6EC2731F-26DF-4897-9ED6-99D78A58BB87@couchbase.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_C37B4E1DE13045AA9A0C466B3DD9D46Ccouchbasecom_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_C37B4E1DE13045AA9A0C466B3DD9D46Ccouchbasecom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable 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 ha= ppening actually. That=92s not true. It depends on the schema. It won=92t 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 C= ouchDB isn=92t going to do it automatically because in some cases it will c= ause mangled documents. =97Jens --_000_C37B4E1DE13045AA9A0C466B3DD9D46Ccouchbasecom_--