You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by ma...@ol-mars.se on 2009/07/13 09:26:01 UTC
How reliable is the versioning system?
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?
Re: How reliable is the versioning system?
Posted by Kai Griffin <ka...@griffinbyteworks.com>.
On 13/07/2009 09:26, maillist@ol-mars.se 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?
>
Couchdb doesn't guarantee the life of document revisions/deletions; they
disappear AFAIK after a database compaction, for example. So you'll
need to build your own revision-tracking system... in fact, that's what
I'm doing for my app.
Cheers,
Kai
Re: Re: How reliable is the versioning system?
Posted by ma...@ol-mars.se.
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" <ja...@jasondavies.com> wrote:
> On 13 Jul 2009, at 08:26, <ma...@ol-mars.se> 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>
>
>
Re: How reliable is the versioning system?
Posted by Jason Davies <ja...@jasondavies.com>.
On 13 Jul 2009, at 08:26, maillist@ol-mars.se 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
www.jasondavies.com