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 cliffywills@aol.com designates
 64.12.206.39 as permitted sender)
Message-ID: <4CA74D6B.8060305@aol.com>
Date: Sat, 02 Oct 2010 16:19:07 +0100
From: Cliff Williams <cliffywills@aol.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.11pre) Gecko/20100928 Shredder/3.1.5pre
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Re: Return doc data with _changes feed?
References: <2E1B2B92-1982-40F2-B885-0CE9737A484C@gmail.com>
In-Reply-To: <2E1B2B92-1982-40F2-B885-0CE9737A484C@gmail.com>
Content-Type: multipart/alternative;
 boundary="------------030100020801090800030901"
X-AOL-SCOLL-URL_COUNT: 0  
x-aol-sid: 3039ac1d29444ca74d6c3998
X-AOL-IP: 92.1.138.210
X-Virus-Checked: Checked by ClamAV on apache.org

--------------030100020801090800030901
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

  Enrique

I think that it is something like

_changes?feed=continuous&include_docs=true

best regards

cliff


On 02/10/10 11:49, Enrique Flores wrote:
> Hi,
>
> We are monitoring a database with the continuous changes API, but our bottleneck now is that we then have to turn around and request the actual doc for every change, is there a way to configure the changes feed to go ahead and return the whole doc instead of just its _id?
>
> thanks,
> Enrique
>
>

--------------030100020801090800030901--