couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Hahn <m...@hahnca.com>
Subject Re: History tracking as a plugin?
Date Mon, 17 Feb 2014 07:29:34 GMT
I keep an update history by using an update handler that adds an entry to
an array in the doc on each update.  Why do you say that MVCC conflicts
with this?  The history matches the actual surviving record from a
collision.


On Sun, Feb 16, 2014 at 11:03 PM, Stanley Iriele <siriele2x3@gmail.com>wrote:

> This may not be too helpful to you but I solved this problem with update
> handlers and a records database..each update returned an update record
> object containing the docid the CTX user old.. All of the old keys and
> new...the new changed keys.
>
> I accumulated them in memory in a server than bulk but them into the
> records db.
>
> This also gave the ability to replay the changes by using a list function
> an folding up that doc ID
> On Feb 16, 2014 10:53 PM, "Jens Alfke" <jens@couchbase.com> wrote:
>
> >
> > 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, so 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
> > documents on the way in, to add properties storing the time and username?
> >
> > --Jens
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message