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 ciprian.craciun@gmail.com
 designates 74.125.83.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAJ_m3YD_V+QDDVVS_rJ-idFysLeHXaf8thmyFpX3voJpdd94MA@mail.gmail.com>
References: 
 <CA+Tk8fw40vD5gjt5Aiv2RxjSSGppopoo3a0RaW363Qhurfpm0Q@mail.gmail.com>
	<CABvT1DFLPxYGttwBDYZxzJoUzoLEjtYFrCZWaOeE=WJOyG9LRQ@mail.gmail.com>
	<CAJ_m3YD_V+QDDVVS_rJ-idFysLeHXaf8thmyFpX3voJpdd94MA@mail.gmail.com>
Date: Tue, 18 Dec 2012 23:38:23 +0200
Message-ID: 
 <CA+Tk8fxqyUma4G3D+rkTP=sjGdxwhpbr_ULD3adeqrpf1mP9qQ@mail.gmail.com>
Subject: Re: How to find the change sequence of a document's revision
From: Ciprian Dorin Craciun <ciprian.craciun@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8

On Tue, Dec 18, 2012 at 11:02 PM, Paul Davis
<paul.joseph.davis@gmail.com> wrote:
> While it won't appear in the changes feed, they do track the
> update_seq they originally had IIRC. I sure don't think we surface
> that anywhere.
>
> Ciprian, is there a specific need for this or is this for something
> app specific?


    I've written a separate email to describe what I want to achieve,
with the subject:
      Simple "transactional" access (i.e. "repeatable reads")