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 4D8A7D497 for ; Wed, 26 Sep 2012 01:00:11 +0000 (UTC) Received: (qmail 30059 invoked by uid 500); 26 Sep 2012 01:00:09 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 30030 invoked by uid 500); 26 Sep 2012 01:00:09 -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 30021 invoked by uid 99); 26 Sep 2012 01:00:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 01:00:09 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.217.180] (HELO mail-lb0-f180.google.com) (209.85.217.180) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 01:00:04 +0000 Received: by lbbge1 with SMTP id ge1so906150lbb.11 for ; Tue, 25 Sep 2012 17:59:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:content-type:x-gm-message-state; bh=9YjtuzUhUZqLcHJl48Fik4k96KT8sDMAdWRsFJ/I5vo=; b=XEKdViMx39HUn0QBfSSedNl5aakdQdDXuV7d+/wODS6EFvlMdGZgmL9I75gt1QM9xi H+EOyXWzmgd0jpnRfylETPnYQEwdWiGaN/9zSwH9krhQuz6+U5dlElA4+MTxtc6Rmpqv DNl8fUQ6L25iudvDqqsZNzGpMbTx3VafxHrwVRuilMebFlYtu8ggv4cc+O+gms7DDBAm 2qMyUXJ7lQCv9hjaCSD92ndcAHc5jFojvNLjWIEeaxtHZFkmCdhmkzeYkNqxFjswbR1K nWlFhLkAGdIn/OAdQ069WUFeL+hrih1IMHhpK/vv1XLuje5NrPNQTrtaKHm+XDq/41IY Y1zQ== Received: by 10.152.110.74 with SMTP id hy10mr11274026lab.54.1348621182079; Tue, 25 Sep 2012 17:59:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.74.196 with HTTP; Tue, 25 Sep 2012 17:59:20 -0700 (PDT) X-Originating-IP: [68.5.117.177] In-Reply-To: References: <6D6F51F2-9DE5-4CBB-9FB0-9511A863B972@apache.org> From: Mark Hahn Date: Tue, 25 Sep 2012 17:59:20 -0700 Message-ID: Subject: Re: following fast doc updates To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=bcaec54ee8c87e909304ca905669 X-Gm-Message-State: ALoCoQkRPqBtcKnxrP+y/jTEhj1kxYbhSq20SrO1+YyYqDUa8vwY6qf+HVmyB8kHoYRFCyfHPj5q X-Virus-Checked: Checked by ClamAV on apache.org --bcaec54ee8c87e909304ca905669 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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 wrote: > > On Sep 25, 2012, at 11:31 AM, Mark Hahn 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 las= t > one you knew about. If there are, you can fetch those too. > > =97Jens > --bcaec54ee8c87e909304ca905669--