Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 76734 invoked from network); 31 Mar 2011 22:11:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 31 Mar 2011 22:11:18 -0000 Received: (qmail 85339 invoked by uid 500); 31 Mar 2011 22:11:16 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 85217 invoked by uid 500); 31 Mar 2011 22:11:16 -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 85209 invoked by uid 99); 31 Mar 2011 22:11:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Mar 2011 22:11:16 +0000 X-ASF-Spam-Status: No, hits=1.8 required=5.0 tests=FREEMAIL_FROM,FREEMAIL_REPLY,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of luismiguelferreirasilva@gmail.com designates 209.85.210.180 as permitted sender) Received: from [209.85.210.180] (HELO mail-iy0-f180.google.com) (209.85.210.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Mar 2011 22:11:09 +0000 Received: by iyf40 with SMTP id 40so4112021iyf.11 for ; Thu, 31 Mar 2011 15:10:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type:content-transfer-encoding; bh=k98Byj/hGRVdivVnn2tQnwMFLNnQppb4mrOG1jwbUDU=; b=tc6FqEK7TTRJmIjCSNmOEXy8ElVYtMqVh1LfPKtub2l3V0Z4+3DPDfOn2wazEboanh w+zdkPaqNknnInYu8RuZ7Htz7AAonb+/IRfWHfCM5/2BdBAbBggl+2Z2Pwzn+B35P7Fa V3Ri44ThEQhKhnVvEgO7tGUk3yJ0wOt8aS4vU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=C9W1Za3RakKRn9Sp4cW948ksiM9bOaZoGbiCaX4Mzt6O6OaaJ62TjaHV1a8wCx7yLy jnFQ/JVBW49RkHLZsC8P7AsMPo1fKqBUxYiRPGJkntph80CJkl7eGk/XDELca9vC5iJJ SesAavysFrqBp0JZ465rW3gqSVLl5IsJmmUUs= Received: by 10.42.135.200 with SMTP id q8mr3922811ict.32.1301609448128; Thu, 31 Mar 2011 15:10:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.12.75 with HTTP; Thu, 31 Mar 2011 15:10:28 -0700 (PDT) In-Reply-To: References: From: Luis Miguel Silva Date: Thu, 31 Mar 2011 16:10:28 -0600 Message-ID: Subject: Re: DocumentRevisions - any way to make sure they will always be available? To: user@couchdb.apache.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Thanks, Brian pointed me to the guide! :o) Are the change notifications part of the current product? Or something like the "https" capability (which only work in 1.1)? On Thu, Mar 31, 2011 at 3:29 PM, Sean Copenhaver wrote: > Heh, yeah I should have been a bit more explicit. I was talking about the > _changes API. > > I would suggest checking out the free book and skimming over the wiki if = you > are not too familiar with CouchDB: > > http://guide.couchdb.org/ > http://wiki.apache.org/couchdb/ > > > On Thu, Mar 31, 2011 at 5:20 PM, Luis Miguel Silva < > luismiguelferreirasilva@gmail.com> wrote: > >> Dear Sean, >> >> Is there an easy way to listen for changes?? Does CouchDB provide us >> with a mechanism to do it? >> >> Does anybody have any suggestions on how i should do it? >> >> p.s. thanks to all who answered my question [Sean, Paul and David]! (i >> dont want to send out individual emails to avoid spamming) ;o) >> >> Thanks, >> Luis >> >> On Thu, Mar 31, 2011 at 3:02 PM, Sean Copenhaver >> wrote: >> > The revision tree is I believe to help keep track of things for >> replication >> > (not positive of this) as well. So it's really an internal mechanism t= hat >> we >> > have access to. >> > >> > You could have something listening on _changes and perform this >> revisioning >> > and change tracking yourself. Not self contained, but doable. >> > >> > On Thu, Mar 31, 2011 at 4:51 PM, Paul Davis > >wrote: >> > >> >> On Thu, Mar 31, 2011 at 4:43 PM, Luis Miguel Silva >> >> wrote: >> >> > Dear all, >> >> > >> >> > I'm very interested in CouchDB's DocumentRevision features because = i >> >> > want to be able to store historical data so i can later consume it = and >> >> > see how it progressed over time. >> >> > So my idea would be to simply add a timestamp and that timestamp >> >> > SHOULD be enough to let me know a new revision has been registered. >> >> > >> >> > The thing is, according to the documentation, we cannot guarantee t= he >> >> > revisions will be available once the DB is compacted: >> >> > http://wiki.apache.org/couchdb/HTTP_Document_API >> >> > >> >> > But...what is the point of this then? Is there a way to always make >> >> > revisions available? >> >> > >> >> > Also, is it possible to only get the fields that changed between tw= o >> >> > revisions?? That would be A-W-E-S-O-M-E for what i need to do :o). >> >> > >> >> > Thanks in advance, >> >> > Luis >> >> > >> >> >> >> MVCC tokens are not to be used for revision control. >> >> >> >> If you need revision control, you need to build it yourself. >> >> >> > >> > >> > >> > -- >> > =93The limits of language are the limits of one's world. =93 -Ludwig v= on >> > Wittgenstein >> > >> > > > > -- > =93The limits of language are the limits of one's world. =93 -Ludwig von > Wittgenstein >