Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jchris@gmail.com designates
 74.125.92.145 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=h/leUlJ4bAF0TktqDXlOXtIiS8J5SdUOzt8ikDdicudbGWmHh8wifHsF/mzCswnxT/
         tAqdzO9IqO1GKnrcLTiofLrRURfGagjWZreeIV2fOk0TcSslvCU5HnvIOmlL2vagQsAo
         vSG1SHtYKglKl8hay1rBKc3L5h7WNrUSp0+SU=
Message-ID: <e282921e0808050930l560cd659wc31ba8be337a0b5a@mail.gmail.com>
Date: Tue, 5 Aug 2008 09:30:24 -0700
From: "Chris Anderson" <jchris@grabb.it>
Sender: jchris@gmail.com
To: couchdb-user@incubator.apache.org
Subject: Re: Optionally including docs in view results
In-Reply-To: <9DF72862-153C-4752-92E0-5DA4EF65CDE1@blit.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <48974B09.5080807@inflatablecookie.com>
	 <e282921e0808041140s4e9f447as4eae06ca2759edb@mail.gmail.com>
	 <e282921e0808041157w10ab39e2xa642692719d443da@mail.gmail.com>
	 <489752DF.2030603@inflatablecookie.com>
	 <e282921e0808041418v68b92e64t8989277d04384235@mail.gmail.com>
	 <489775CC.3010707@inflatablecookie.com>
	 <64a10fff0808041442r6d864058rd923b494207a7882@mail.gmail.com>
	 <e282921e0808041447o73b1394axe65cc27f228110f2@mail.gmail.com>
	 <9DF72862-153C-4752-92E0-5DA4EF65CDE1@blit.com>

On Tue, Aug 5, 2008 at 9:02 AM, Troy Kruthoff <tkruthoff@blit.com> wrote:
> +1 for the bulk_docs api, specifically being able to perform multiple
> REST-type operations in a single request should be "bulk_docs" by
> definition.
>

Part of the complexity comes from the fact that _bulk_docs is already
used in replication, so it has some options that aren't normally used
in a standard POST from an application.

Currently with _bulk_docs you can do the equivalent of PUT
(create/update with _id), POST (create without _id), and DELETE
(update set _deleted=true). So most of the RESTful options are
available, they just aren't segregated by verb.

You can't do GET yet - to me it just seems confusing to allow both
modification of documents and fetching of documents in the same http
request.

If I'm wrong, and we really should include document fetches in
_bulk_docs, it won't be impossible to code, but we should make sure
the feature is clear.

The POST body can certainly accommodate both "docs" and "ids" members,
its just a matter of how to structure the response so that it's clear
which parts of the response come from which CouchDB actions. (Not to
mention all the edge-cases around documents that are both updated by
the "docs" member, and requested by the "ids" member, or maybe the
update phase succeeds but one of the request docs is 404.)

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