Ok, thanks guys, I'll just have to manage my resources myself. That's probably the best solution for me anyway :)
On Jul 13, 2009 09:52 "Jason Davies" <[email protected]> wrote: > On 13 Jul 2009, at 08:26, <[email protected]> wrote: > > > I'm about to build a system of resources where every change to a > > resource are supposed to be loggable and traceable. Can I trust the > > revision/versioning system in couch to handle this for me, or do I > > want > > to build my own data structure for storing revisions of each > > resource? > > You'll want to build your own data structures for revision control. > > In CouchDB, the "_rev" (revision) field is only used for multiversion > concurrency control (MVCC). Old revisions of documents are only kept > around until the next compaction and they are never replicated, so we > don't recommend using this for any kind of revision control system and > we advise that you roll your own. > > -- > Jason Davies > > <http://www.jasondavies.com> > >
