From user-return-20565-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Thu Apr 19 23:01:44 2012 Return-Path: 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 5CCBA998F for ; Thu, 19 Apr 2012 23:01:44 +0000 (UTC) Received: (qmail 73025 invoked by uid 500); 19 Apr 2012 23:01:42 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 72970 invoked by uid 500); 19 Apr 2012 23:01:42 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 72961 invoked by uid 99); 19 Apr 2012 23:01:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Apr 2012 23:01:42 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dominic.tarr@gmail.com designates 209.85.212.52 as permitted sender) Received: from [209.85.212.52] (HELO mail-vb0-f52.google.com) (209.85.212.52) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Apr 2012 23:01:36 +0000 Received: by vbzb23 with SMTP id b23so8599809vbz.11 for ; Thu, 19 Apr 2012 16:01:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=1f48qPaDrh7HEq3kHbTl/txMd6KATQ1ehBKyLs5XcnI=; b=DDH5FPUn8z8BZnCc7mwPxFRQCic0XvSfzGybCT0qz58oPwPR1zqb7RzA+6e065m3kH 88xqDJ5+coMZf0dJ5MTaftrL1AUuoT3p9FdLd7mBeNFEycnpbzjiJm8aMpCr7GJnSavp T5uep7EQQhg0zCtGIHXQw8nWkeGoMBjNirxnQMaQ1UR9utraAX+o8dgS0rQn8LqTOAxZ 1Kvutyzx8QyZ7RpqHaPTuG2+DqgbD7TbJHao//RSv/gMJ7cY28B47M2HG5/wvRaPfKE0 GXl/6RstQQNrsrMPZZwUGjVIHPMFJd4So2Bxp6CUNTMY8tdexHkfouGr/MAGCd5Rf5Fl Sqxw== MIME-Version: 1.0 Received: by 10.52.65.170 with SMTP id y10mr1830325vds.48.1334876475085; Thu, 19 Apr 2012 16:01:15 -0700 (PDT) Received: by 10.52.166.230 with HTTP; Thu, 19 Apr 2012 16:01:14 -0700 (PDT) In-Reply-To: References: Date: Fri, 20 Apr 2012 11:01:14 +1200 Message-ID: Subject: Re: suggestion for improvement From: Dominic Tarr To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=20cf307f3af21dd2d804be102606 --20cf307f3af21dd2d804be102606 Content-Type: text/plain; charset=ISO-8859-1 I'm think mark wants to know what has changed with the last update, rather than to keep every version around forever. On Fri, Apr 20, 2012 at 10:10 AM, Robert Newson wrote: > You can fetch previous revisions with ?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 wrote: > > Thanks, I had forgotten about open_revs. But open_revs only applies to > > conflicts, right? > > > > How do I find out what changed in a change feed? In other words, if I > get > > a change feed is there a way to access the previous version to find out > > what changed? > --20cf307f3af21dd2d804be102606--