Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Wed, 27 Mar 2013 16:09:15 +0000 (UTC)
From: "Dave Cottlehuber (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12639352.1364400517964.64324.1364400555613@arcas>
In-Reply-To: <JIRA.12639352.1364400517964@arcas>
References: <JIRA.12639352.1364400517964@arcas>
Subject: [jira] [Created] (COUCHDB-1723) conflicts are the rule, not the
 exception
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Dave Cottlehuber created COUCHDB-1723:
-----------------------------------------

             Summary: conflicts are the rule, not the exception
                 Key: COUCHDB-1723
                 URL: https://issues.apache.org/jira/browse/COUCHDB-1723
             Project: CouchDB
          Issue Type: Improvement
            Reporter: Dave Cottlehuber


All previous versions of CouchDB hide conflicts by default (selecting
an arbitrary but consistent winning revision). Expert users can find
and resolve conflicts.

Instead, expose the true picture by default, this includes;

* Reading a document with conflicts returns all conflicting versions,
not just the winner. This might manifest as the ?conflicts=true
response or could be a 300 (Multiple Choices) response.

* Always accept a write (as long as it passes all validate_doc_update
functions). This means that no response will give a 409 (Conflict) by
default. You can still insist on a matching revision by using the
If-Match header.

* _rev is frequently assumed to be a user-facing revision/versioning
system, our efforts to convince otherwise have failed. Embrace this
also and rename the field to _mvcc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira