incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Hahn <m...@hahnca.com>
Subject Re: following fast doc updates
Date Wed, 26 Sep 2012 00:59:20 GMT
Thanks for the response.

> you can fetch that revision with its history,

I am already using a scheme that requires me to store the latest revision
number for every doc in memory.  You scheme would also require that and it
would cause extra reads.  Correct me if I'm wrong.

On Tue, Sep 25, 2012 at 5:46 PM, Jens Alfke <jens@couchbase.com> wrote:

>
> On Sep 25, 2012, at 11:31 AM, Mark Hahn <mark@hahnca.com<mailto:
> mark@hahnca.com>> wrote:
>
> The _changes feed only ever shows leaf revisions
>
> AARRGGHH.  I am so screwed.  I have been working on a scheme that relies on
> tracking every change.  And as everyone knows there is normally no way to
> find out what changed in a doc.  I am going to have to add a history of
> changes to each doc which it not only wasteful, but a pain to implement.
>
> Seems like this should be doable. When the _changes feed says a doc has
> changed, you can fetch that revision with its history, then look at the
> history to see whether there are any intermediate revisions after the last
> one you knew about. If there are, you can fetch those too.
>
> —Jens
>

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