On Feb 8, 2014, at 6:32 AM, Systematic Frank <[email protected]<mailto:[email protected]>> wrote:
Recently I have come to a case where CBL is highly desirable not because the replication, but because of the great json/dictionary based views and map-reduce. Ha! That's flattering -- sometimes I think that the only reason people put up with the low-level nature of map/reduce, instead of fancy SQL queries, is because they need the sync features :) Sometime ago I discovered that some features had a default behavior that could not be changed. In the case where I do not care about replication, I would like to disable: 1. previous document versions You can now accomplish something close to that by changing the database's .maxRevTreeDepth property, which controls the number of old revisions that it will keep track of. (This refers to the metadata, not the document bodies; non-current doc bodies always get deleted during compaction, but the metadata of old revisions normally stays around to help with conflict resolution.) You should be able to set db.maxRevTreeDepth to 1, and all old revision data will get deleted whenever you compact the database. It won't be quite as lightweight as it could be, because the old revisions do get kept until the compaction occurs, but it should be OK. 2. not keeping around deleted documents You can do this by purging a document immediately after deleting it. But there's no mode that would make this happen automatically. --Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/E215553B-6A3B-4001-B833-13375A0724BB%40couchbase.com. For more options, visit https://groups.google.com/groups/opt_out.
