Fixtures appear to be subject to database compaction

[shackpank]

CouchDB has a "compaction" process, which will delete old revisions of documents past a configurable maximum, by default 1000. Normally this job is manually run, but SaaS providers (such as cloudant) schedule it automatically, which can result in fixtures mysteriously disappearing if you have enough tests or if you refixture them frequently enough.

On cloudant this can be worked around by increasing the maximum:

curl -X PUT -d "a-really-big-number" https://api-user:[email protected]/database/_revs_limit

...but I'm wondering if a change to how the documents are stored could exempt them from being candidates for deletion during compaction?