Hmm, what a smart way to do it! Thanks a lot! :o) I just didn't fully understood if the changes this guy made to the jquery core are now part of the standard couchDB distribution or not? And WHAT i exactly have to do to implement his theory (i understood the theory and love it, i just didn't understand the execution part :oP).
Thanks, Luis Miguel Silva On Mar 31, 2011, at 5:27 PM, Nils Breunese <[email protected]> wrote: > No, don't use MVCC _revs for versioning. Check out > http://blog.couchbase.com/simple-document-versioning-with-couchdb for a way > to do simple versioning. > > Nils. > ________________________________________ > Van: Luis Miguel Silva [[email protected]] > Verzonden: donderdag 31 maart 2011 22:43 > Aan: [email protected] > Onderwerp: DocumentRevisions - any way to make sure they will always be > available? > > 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 > ------------------------------------------------------------------------ > VPRO www.vpro.nl > ------------------------------------------------------------------------
