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 paul.joseph.davis@gmail.com
 designates 209.85.132.242 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=CQmsX7KIIP8kthToV23/K4bh5CqoPCE2td8q7Bs0JGI88dxZ/dSlYypsEOUjLZjixA
         RNvHFQBYM3xuIpryugx0f31zNVWUFnrArzAYaMBMrBqMnlkts16te3k3QPUKnAc2yL4U
         UVz5VEzVfo+zusZpdWaFTx+ypT+YkKyou5U10=
MIME-Version: 1.0
In-Reply-To: <e8d26ac40904031304ie9e30d6r520a2772c7e84365@mail.gmail.com>
References: <e8d26ac40904031132o6a475defo2ea61e136b253470@mail.gmail.com>
	 <e2111bbb0904031159k46d2f701ofc58da213aa8335f@mail.gmail.com>
	 <e8d26ac40904031304ie9e30d6r520a2772c7e84365@mail.gmail.com>
Date: Fri, 3 Apr 2009 16:13:40 -0400
Message-ID: <e2111bbb0904031313n2686334cmd46a05e15272ca6a@mail.gmail.com>
Subject: Re: rev of aggregate results
From: Paul Davis <paul.joseph.davis@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 3, 2009 at 4:04 PM, Adam Wolff <awolff@gmail.com> wrote:
> Oh, I'm not concerned that I'm not seeing the most recent info -- just
> wondering what's the fastest way to find out if the application has
> the most recent data.
>
> Tell me more about "view tags." That may be exactly what I'm looking
> for. Is that an ETAG for the view results?
>

Exactly. I should've been more specific. Also, it looks like etags are
already in.

> A
>
> On Fri, Apr 3, 2009 at 11:59 AM, Paul Davis <paul.joseph.davis@gmail.com>=
 wrote:
>> Maybe I'm missing something, but assuming you're not using the
>> stale=3Dok flag you should be guaranteed that the view you're seeing is
>> the most recently completed update after your request was received.
>> Ie, it'll wait if the view is being updated.
>>
>> If view tags are in trunk that'd capture the information on the state
>> of the btree. I'm not sure if that patch has made it in yet though.
>>
>> Or I could be way off base with what you're asking.
>>
>> HTH,
>> Paul Davis
>>
>> On Fri, Apr 3, 2009 at 2:32 PM, Adam Wolff <awolff@gmail.com> wrote:
>>> Hi,
>>> I've noticed a pattern that appears in a couple of places in our app.
>>> We have views which return multiple documents for a given key. What's
>>> the fastest way that we can determine if we have the current rev of
>>> the view, if we define a view's rev as the id and revs of all the
>>> documents in the view?
>>>
>>> The solution I've thought of so far is to write the view's map
>>> function like this:
>>>
>>> map : function(doc){
>>> =A0 var key =3D computeKey(doc);
>>> =A0 emit([key, doc.id, doc.rev], null);
>>> }
>>>
>>> We query the view with startkey=3D[key, null, null]&endkey=3D[key, {}, =
{}]
>>> and the rev for that key is just the text of the response. We haven't
>>> gotten all the way through this, but it sees like it should work. My
>>> concern is that this string will get unwieldy when there are a lot of
>>> docs in the result set.
>>>
>>> Is there a recipe for determining the rev of a document collection?
>>> Something in the semantics of id or rev that I've missed?
>>>
>>> Thanks in advance,
>>> Adam
>>>
>>
>