Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of
 luismiguelferreirasilva@gmail.com designates 209.85.160.52 as permitted
 sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:from:date:message-id:subject:to:content-type;
        b=js6UcFtXdQQtYxefLpwgC8NTIWcGQ7Vf48CuIUv7PYGVnIC9HlxtpEEFwa57V50EqH
         C4F4XvaBJcovZOzsOKa0pGu+rnvxDaFleYeWsoxBfsSGQMvq3nmIcqYMuGckGbWNA0+N
         QVPl81VHI83zMJEhAqiFyjNJTjorTWAlxp088=
MIME-Version: 1.0
From: Luis Miguel Silva <luismiguelferreirasilva@gmail.com>
Date: Tue, 5 Apr 2011 15:46:10 -0600
Message-ID: <BANLkTimC8=Py=P6wRf2DcpdtFdHcCMOzqA@mail.gmail.com>
Subject: Update conflicts?
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Dear all,

I'm trying to play around with updates and i'm bumping into some problems.

Let's image we have to clients that poll a document from the server at
the same time and get the same _rev.
Then one of them updates the doc based on the _rev it got:
[root@xkitten ~]# curl -X PUT -d
'{"_rev":"3-0d519bcf08130bf784f3c35d79760740","hello2":"fred2"}'
http://localhost:5984/benchmark/test?conflicts=true
{"ok":true,"id":"test","rev":"4-03640ebafbb4fcaf127844671f8e2de7"}
Then another one tries to update the doc based on the same exact _rev:
[root@xkitten ~]# curl -X PUT -d
'{"_rev":"3-0d519bcf08130bf784f3c35d79760740","hello3":"fred3"}'
http://localhost:5984/benchmark/test?conflicts=true
{"error":"conflict","reason":"Document update conflict."}
[root@xkitten ~]#

Is there a way to avoid this?! (like...make the update just create a
new _rev or something)??

Ideally, we would be able to update without specifying the _rev, just
posting (or, in this case PUTting) to the document...

Thoughts??

Thank you,
Luis