From user-return-7786-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Sun Nov 29 22:23:57 2009 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 76493 invoked from network); 29 Nov 2009 22:23:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Nov 2009 22:23:56 -0000 Received: (qmail 46701 invoked by uid 500); 29 Nov 2009 22:23:55 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 46618 invoked by uid 500); 29 Nov 2009 22:23:55 -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 46608 invoked by uid 99); 29 Nov 2009 22:23:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Nov 2009 22:23:55 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jchris@gmail.com designates 209.85.216.195 as permitted sender) Received: from [209.85.216.195] (HELO mail-px0-f195.google.com) (209.85.216.195) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Nov 2009 22:23:52 +0000 Received: by pxi33 with SMTP id 33so2065855pxi.28 for ; Sun, 29 Nov 2009 14:23:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=oAoxASg+wHWYJ6newlgZ/HghJznamBRiwe5bv+2oPgQ=; b=F0rLczhu/yPzpg9rt5q+AuPEkR1kDEIjtMpFVSWIWhE5cbgm3VttGigug94OOFvw0q OGCO0tGNB+tXn0q1bpNo2v52IcbUoUClGIduQcMaCWNt3MgfcqdlpyRzdf+1m8OFp1Kl cGUylDiDaWNVLW/+NjKMu3+L8iXIdz4SOMTqE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=IhGHVuGHn0Q0gnL0frIyx1H9hUSUrIdhmz+zEY+miQc4sIGpl30SJk/Y1X5p7A92Sc jRf/iuqF++FkHGoU82Y/8q11CVI25ouncyhI1f49ZaJWVctecbz7pVdm1r17fA5PtNUW 0UOcTduk79m9NGuGDjmZHlVO+YXZhsGBqDQdU= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.143.27.2 with SMTP id e2mr354412wfj.202.1259533412215; Sun, 29 Nov 2009 14:23:32 -0800 (PST) In-Reply-To: References: <20091129.095942.28213.0@webmail20.dca.untd.com> <4B12B1D4.3050005@gmx.de> Date: Sun, 29 Nov 2009 14:23:32 -0800 X-Google-Sender-Auth: 150ff7b03cbd9512 Message-ID: Subject: Re: filters for _changes dont seem to work From: Chris Anderson To: user@couchdb.apache.org Cc: Sebastian Cohnen Content-Type: text/plain; charset=ISO-8859-1 On Sun, Nov 29, 2009 at 12:55 PM, Sebastian Cohnen wrote: > Hey Chris, > > On 29.11.2009, at 20:05, Chris Anderson wrote: > >> To be clear, the _changes API doesn't guarantee that you'll get every >> single change. If a document is changed many times in quick succession >> it's possible that only the latest state will appear in the _changes >> feed. > > okay, that was not the way I understood the _changes-feed. Is there an API interface that guarantees me to tell all changes? > No, there is no API for that. I think you'll find the _changes API is actually what you want. If a document is changed, you are guaranteed to be notified, it's just that if the same document is changed lots of times, you may not see all the intermediate states. This behavior is inherent in CouchDB's data-model, as it is used to drive replication, view indexing, and external indexers. Hopefully it works for your purposes as well. Chris PS thanks for adding to the ticket, Roger. -- Chris Anderson http://jchrisa.net http://couch.io