Mailing-List: contact couchdb-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jchris@gmail.com designates
 74.125.44.158 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=rjc/jJ8ap1M3oevyVmWZUig0Pk7XtZVb/TWa9jaIsFrfE6LD9Wy6pWeIr08+8ERl1R
         u/ze/1YV+myC4Gbsx7Ynit3pYhtf9el/is9EXKHyDgkjprjHUnSTEi3GXwGRe6fvQ9co
         PbkbL6Kgzx3gLNnzg1VAFgaFPKRtWFyOE75mY=
Message-ID: <e282921e0812031656m153e7a77v391d2226b9a5e322@mail.gmail.com>
Date: Wed, 3 Dec 2008 16:56:26 -0800
From: "Chris Anderson" <jchris@apache.org>
Sender: jchris@gmail.com
To: couchdb-dev@incubator.apache.org
Subject: Re: bulk update: deleting and updating
In-Reply-To: <6A48F931-172B-47D9-8959-1AB645278EFB@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20081203163944.GW13753@ginosko.local>
	 <6A48F931-172B-47D9-8959-1AB645278EFB@apache.org>

I like Damien's solution. Michael, have you got the bandwidth to put
together a couch_tests.js patch that shows the error?

On Wed, Dec 3, 2008 at 8:48 AM, Damien Katz <damien@apache.org> wrote:
> It's not intended behavior, but I'd say just don't do that. Editing the same
> document twice in a bulk update is not supported. Maybe we should add an
> explicit check and return an error.
>
> -Damien
>
> On Dec 3, 2008, at 11:39 AM, Michael Hendricks wrote:
>
>> What should be the proper behavior for a bulk update request which
>> asks to delete a document and to update it at the same time?  For
>> example:
>>
>>   POST http://127.0.0.1:5984/net-couchdb-11942-61931/_bulk_docs
>>   Accept: application/json
>>   Content-Length: 104
>>
>>
>> {"docs":[{"_deleted":true,"_id":"drei","_rev":"683265243"},{"_id":"drei","third":3,"_rev":"683265243"}]}
>>
>> Until recently (r713132), CouchDB returned a 412 response to indicate
>> that there was a conflict.  That seems like the right thing to do.
>> The new response seems broken:
>>
>>   HTTP/1.1 201 Created
>>   Cache-Control: must-revalidate
>>   Date: Wed, 03 Dec 2008 16:24:15 GMT
>>   Server: CouchDB/0.9.0a-incubating (Erlang OTP/R12B)
>>   Content-Length: 89
>>   Content-Type: application/json
>>   Client-Date: Wed, 03 Dec 2008 16:24:15 GMT
>>   Client-Peer: 127.0.0.1:5984
>>   Client-Response-Num: 15
>>
>>
>> {"ok":true,"new_revs":[{"id":"drei","rev":"2472902046"},{"id":"drei","rev":"965136091"}]}
>>
>> In other words, it created two new revisions for the same document.
>> Is that intended behavior?
>>
>> --
>> Michael
>
>


-- 
Chris Anderson
http://jchris.mfdz.com