incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Copenhaver <sean.copenha...@gmail.com>
Subject Re: DocumentRevisions - any way to make sure they will always be available?
Date Thu, 31 Mar 2011 21:29:19 GMT
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
> <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 that
> 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.com
> >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 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 the
> >> > 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.
> >>
> >
> >
> >
> > --
> > “The limits of language are the limits of one's world. “ -Ludwig von
> > Wittgenstein
> >
>



-- 
“The limits of language are the limits of one's world. “ -Ludwig von
Wittgenstein

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message