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 <[email protected]>wrote: > On Thu, Mar 31, 2011 at 4:43 PM, Luis Miguel Silva > <[email protected]> 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
