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 robert.newson@gmail.com
 designates 209.85.210.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <56490C6A-8686-4B2D-ADB2-BA93EEBE03EF@couchbase.com>
References: <56490C6A-8686-4B2D-ADB2-BA93EEBE03EF@couchbase.com>
Date: Thu, 14 Jul 2011 19:01:30 +0100
Message-ID: 
 <CABvT1DFYqUi7UdP1Gz=LmUH9M5FLgLH-04V5stFXjx7HSoZYwg@mail.gmail.com>
Subject: Re: Starting _changes from the current sequence number?
From: Robert Newson <robert.newson@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

It's been proposed (?since=3Dnow, iirc) but hasn't happened.

On 14 July 2011 18:40, Jens Alfke <jens@couchbase.com> wrote:
> For my purposes I want to use the _changes feed to get notified of future=
 changes to the database, but not of historical changes. So essentially I w=
ant to pass =93the current sequence number=94 as the value of the ?since pa=
rameter. This seems like a common pattern =97 is there any easy shorthand f=
or this, other than first GETting the database URL and looking up the updat=
e_seq property?
>
> =97Jens