Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of sean.copenhaver@gmail.com
 designates 209.85.220.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=wAztOlsbUaoVmcoed3HK6qPb/wjFcW1DM6slSq6Jgcm+/ktLnrnGf6oPBLRcWIRZnj
         93I4FTcJMDH90uThKbGfIaAXlphkt5WCotzaEYWsx7hoIVoHp4gDQFcmBdIvVXKbMg6z
         ss8k7pQ3x+ikZdNaPtffsmj8Sl3RyFDMmp0fY=
MIME-Version: 1.0
In-Reply-To: <AANLkTinLenrSgVd84vaa3XVL6OeUwGGC3fQzbBWTT0k8@mail.gmail.com>
References: <AANLkTikOePf5sAVeE_5vq-dZuP+qZ6N69kbHfinfSUeV@mail.gmail.com>
	<AANLkTim4Fw-ODqcg5ZAOBHRhF7xSt=Xk-fU15jap=Tu2@mail.gmail.com>
	<AANLkTimZ4+j_GeGoa44_fTtfe+qCACDgu2EDp=o8A5q2@mail.gmail.com>
	<AANLkTinLenrSgVd84vaa3XVL6OeUwGGC3fQzbBWTT0k8@mail.gmail.com>
Date: Thu, 31 Mar 2011 17:29:19 -0400
Message-ID: <AANLkTi=wTRUa9t7Fxi5VGXc816yQUwzKsXxdUH2Bb2Bj@mail.gmail.com>
Subject: Re: DocumentRevisions - any way to make sure they will always be
 available?
From: Sean Copenhaver <sean.copenhaver@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=bcaec5016397763e39049fcdfce9

--bcaec5016397763e39049fcdfce9
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

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 yo=
u
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
> <sean.copenhaver@gmail.com> 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 th=
at
> 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 <paul.joseph.davis@gmail.co=
m
> >wrote:
> >
> >> On Thu, Mar 31, 2011 at 4:43 PM, Luis Miguel Silva
> >> <luismiguelferreirasilva@gmail.com> 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 a=
nd
> >> > 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 th=
e
> >> > 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 two
> >> > 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 vo=
n
> > Wittgenstein
> >
>


--=20
=93The limits of language are the limits of one's world. =93 -Ludwig von
Wittgenstein

--bcaec5016397763e39049fcdfce9--