couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Cottlehuber (JIRA)" <>
Subject [jira] [Updated] (COUCHDB-1723) conflicts are the rule, not the exception
Date Wed, 27 Mar 2013 16:49:16 GMT


Dave Cottlehuber updated COUCHDB-1723:

    Labels: couchdb, erlang, gsoc2013, javascript rest,  (was: )
> conflicts are the rule, not the exception
> -----------------------------------------
>                 Key: COUCHDB-1723
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>            Reporter: Dave Cottlehuber
>              Labels: couchdb,, erlang,, gsoc2013,, javascript, rest,
> 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:

View raw message