We have a new wiki. The migration is not 100% complete. You can help out by moving pages across. This wiki will exist for as long as there are pages left.

The official documentation has moved to http://docs.couchdb.org — The transition is not 100% complete, but http://docs.couchdb.org should be seen as having the latest info. In some cases, the wiki still has some more or older info on certain topics inside CouchDB.

You need to be added to the ContributorsGroup to edit the wiki. But don't worry! Just email any Mailing List or grab us on IRC and let us know your user name.


CouchDB does not overwrite updated documents in place, instead it creates a new document at the end of the database file, with the same _id but a new _rev identifier. This type of storage system is space-wasteful so regular Compaction is needed to reclaim disk space. Note that the older revisions are not available to Views.

Document revisions are used for optimistic concurrency control. If you try to update a document using an old revision the update will be in conflict. These conflicts should be resolved by your client, usually by requesting the newest version of the document, modifying and trying the update again.

@@ How does this relate to replication conflicts?

Revision History

You cannot rely on document revisions for any other purpose than concurrency control.

Due to compaction, revisions may disappear at any time. You cannot use them for a client revision system.

Replication has also an impact on revisions, i.e. Replication only replicates the last version of a document, so it will be impossible to access, on the destination database, previous versions of a document that was stored on the source database.

If you wish to implement revisions in your client system, a number of patterns have been suggested:

@@ Please add to this list and flesh out the solutions as you see fit.

Document_revisions (last edited 2011-11-23 15:11:19 by 62)