incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zachary Zolton <>
Subject Re: version history
Date Thu, 13 May 2010 14:53:54 GMT
@Cory, you might wanna check out the bit on "event sourcing" from the wiki:

On Thu, May 13, 2010 at 4:40 AM, Sebastian Cohnen
<> wrote:
> CouchDB itself does not provide a "version history" of documents. the _rev field is used
as an MVCC token. If you need version-tracking, you need to implement it by yourself.
> On 13.05.2010, at 11:01, Cory Zue wrote:
>> Hi CouchDBers,
>> I'm attempting to use CouchDB for a system that requires full auditing
>> of all data operations. Because of its built in revision-tracking,
>> couch seemed like an ideal choice. But then I read in the O'Reilly
>> textbook that "CouchDB does not guarantee that older versions are kept
>> around."
>> I can't seem to find much more documentation on this point, or how
>> couch deals with its revision-tracking internally. Is there any way to
>> configure couch either on a per-database, or per-document level to
>> keep all versions around forever? If so, how?
>> Anything you can point me at that would let me know if this is
>> possible and how to do it would be much appreciated.
>> thanks,
>> Cory

View raw message