Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of jens@couchbase.com designates
 206.225.164.31 as permitted sender)
From: Jens Alfke <jens@couchbase.com>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Date: Sun, 16 Feb 2014 22:53:23 -0800
Subject: Re: History tracking as a plugin?
Thread-Topic: History tracking as a plugin?
Thread-Index: Ac8rrPNJf1Elr7+VStCImlCRxvFRlg==
Message-ID: <2F2D15E9-2302-446D-A0EF-B08226B2FA6F@couchbase.com>
References: 
 <CABadZmLKuAnc6pgBgsJRnk-K2pn9-t3uHVfGXRyqUQuwxEYL6Q@mail.gmail.com>
In-Reply-To: 
 <CABadZmLKuAnc6pgBgsJRnk-K2pn9-t3uHVfGXRyqUQuwxEYL6Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On Feb 16, 2014, at 9:50 PM, Suraj Kumar <suraj.kumar@inmobi.com> wrote:

> While we could use "_changes" API, there is no
> way to get the UserCtx. This is the real limitation of changes API due to
> which we are looking for other ways.

It's not a limitation of the changes API, it's a limitation of the database=
 itself. CouchDB simply does not store the information you're asking for, s=
o there's no way for the changes API to discover it.

> What would you recommend is the best way to achieve history tracking?

Maybe put some kind of proxy in front of CouchDB that can modify the docume=
nts on the way in, to add properties storing the time and username?

=97Jens=