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.46.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=csl6+2M/VXaFV6yustcRTV4dA2OvhETValQjRSuGvdqVP+al9d9PyZXNSSeqV00WhC
         om3cP3SD0jp/yuziDUFmZZrU9QhrVbtez7DN3659bghiSOTyIqu1tmRLunEOjWr8U0t7
         dQl0/GnchoyU123L0GJ8fynY4ZUnuQTpzTXz0=
Message-ID: <e282921e0808051206m7f314d87o72fe8100bccaf640@mail.gmail.com>
Date: Tue, 5 Aug 2008 12:06:40 -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: <e2111bbb0808051126mdf2c571u7a140c780e8bfadb@mail.gmail.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>
	 <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>
	 <e282921e0808050930l560cd659wc31ba8be337a0b5a@mail.gmail.com>
	 <e2111bbb0808051126mdf2c571u7a140c780e8bfadb@mail.gmail.com>

On Tue, Aug 5, 2008 at 11:26 AM, Paul Davis <paul.joseph.davis@gmail.com> wrote:
> There was a similar idea posted on another thread that I really liked,
> looked at implementing and got scared of because of the mentioned
> replication stuff in bulk docs.
>
> The basic idea was to be able to post something like the following to _bulk_docs
>
> {
>  "put": {doc1, doc2, doc3}
>  "delete": {doc4, doc5}
>  "get": {doc6}
> }

This idea has its upsides, but I'm wary of breaking
backwards-compatibility with _bulk_docs.

However, I don't see anything wrong with the way _bulk_docs currently
handles create/update/delete (even if it isn't RESTful).

On IRC there have been some good arguments in favor of an include_docs
option for view, which could be used with _all_docs and multi-key view
requests to yield the _load_docs (fetch docs in bulk) feature.

Also with that design Tom's original question on this thread would be
a simple case.


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