CouchDB only remembers the last 1000 _rev values by default (even after compaction). The reason it remembers past _rev values at all is so we can determine common ancestry when merging due to replication. The reason we cut off at 1000 is to avoid the unbounded storage problem of keeping them all.
None of this stops you updating a document as many times as you like. Please show whatever is preventing you from updating, I'm prepared to bet that it is not CouchDB itself. B. On 1 June 2012 23:25, Dave Cottlehuber <[email protected]> wrote: > On 2 June 2012 00:09, Jens Alfke <[email protected]> wrote: >> >> On Jun 1, 2012, at 2:12 PM, Matthias Eck wrote: >> >>> I noticed that a very small number of documents in my database have >>> 1000 revisions, which somehow prevents them from being updated again. >> >> I'm pretty sure CouchDB doesn't have any limit on the number of revisions of >> a document. Perhaps the API/library you're using to access it has a bug that >> breaks with 4-digit revision numbers? What API are you using? > > There is a per-DB limit, _revs_limit, > http://wiki.apache.org/couchdb/HTTP_database_API. Hopefully somebody > will can explain exactly the significance of this, wrt to replication, > stemming, compaction etc. > > A+ > Dave
