Return-Path: 
 <user-return-20564-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org>
X-Original-To: apmail-couchdb-user-archive@www.apache.org
Delivered-To: apmail-couchdb-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id B482399EF
	for <apmail-couchdb-user-archive@www.apache.org>;
 Thu, 19 Apr 2012 22:10:52 +0000 (UTC)
Received: (qmail 43124 invoked by uid 500); 19 Apr 2012 22:10:51 -0000
Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org
Received: (qmail 43090 invoked by uid 500); 19 Apr 2012 22:10:51 -0000
Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@couchdb.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@couchdb.apache.org>
List-Post: <mailto:user@couchdb.apache.org>
List-Id: <user.couchdb.apache.org>
Reply-To: user@couchdb.apache.org
Delivered-To: mailing list user@couchdb.apache.org
Received: (qmail 43081 invoked by uid 99); 19 Apr 2012 22:10:51 -0000
Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Apr 2012 22:10:51 +0000
Received: from localhost (HELO mail-iy0-f180.google.com) (127.0.0.1)
  (smtp-auth username rnewson, mechanism plain)
  by minotaur.apache.org (qpsmtpd/0.29) with ESMTP;
 Thu, 19 Apr 2012 22:10:50 +0000
Received: by iage36 with SMTP id e36so17095147iag.11
        for <user@couchdb.apache.org>; Thu, 19 Apr 2012 15:10:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.50.42.134 with SMTP id o6mr4002531igl.72.1334873449931; Thu,
 19 Apr 2012 15:10:49 -0700 (PDT)
Received: by 10.42.240.135 with HTTP; Thu, 19 Apr 2012 15:10:49 -0700 (PDT)
In-Reply-To: 
 <CACrj35Fr7amGcz7k_zu9E6eGmMi2XVe_0GrvbzcKqDtN+fDwSQ@mail.gmail.com>
References: 
 <CACrj35GSqnowCseHVSLLasXdJDq5QLsZ_emegtxH0KT9s+XKTg@mail.gmail.com>
	<CAPTWwjC=BtofEgGGMkQ=5otpX+HLZVaY1NyV4Fcb4i9BTUt7kQ@mail.gmail.com>
	<CACrj35FPEWRSFs_jS0snKx2y8WQeiHJRhMNaqkLXTkd=7j=1wA@mail.gmail.com>
	<CAPTWwjAvQMoK9geJfkkq+fDShyFk0-DRDA_0X=BVfbco3dWbKA@mail.gmail.com>
	<CAMiZLn0hEN8QW+-05mF2HbrfR9XLz0HTUvZ3vpem2LdW4dw=pg@mail.gmail.com>
	<CACrj35GHtrxWsbn04AACznhzP3zhx5tdMaz0cCF3P6=cFWYJVQ@mail.gmail.com>
	<CABvT1DGv0tgbrcM9mOpfd1Gevs+Sk7pXfONZh+j4bmipNNFa3w@mail.gmail.com>
	<CACrj35Fr7amGcz7k_zu9E6eGmMi2XVe_0GrvbzcKqDtN+fDwSQ@mail.gmail.com>
Date: Thu, 19 Apr 2012 23:10:49 +0100
Message-ID: 
 <CABvT1DGoqy2DQYB0wz91HEUGmB6-SwFVWLQsz6ftsrKOmD1A7g@mail.gmail.com>
Subject: Re: suggestion for improvement
From: Robert Newson <rnewson@apache.org>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

You can fetch previous revisions with ?rev=3D<rev> until compaction
sweeps them away, but it's considered bad practice (your administrator
should be free to compact whenever needed).

I don't think it's CouchDB's job to keep all the old versions of
documents forever, this should be solved at the application layer, it
doesn't seem particularly difficult either. If you care about the
changes a doc goes through, you should record them in the doc itself.
Whenever you update a document, add a new entry to a "history" array,
for example. We have this for replication checkpoints already.

B.

On 19 April 2012 22:33, Mark Hahn <mark@hahnca.com> wrote:
> Thanks, I had forgotten about open_revs. =A0But open_revs only applies to
> conflicts, right?
>
> How do I find out what changed in a change feed? =A0In other words, if I =
get
> a change feed is there a way to access the previous version to find out
> what changed?