[Question] Do we need to clean associated db in production?

[greenais]

Not an issue right now but could be kind of in production - so more sounds like a question:
connect warns that MemoryStore usage not recomended in production due to memory leaks (in fact it is as they still dind't implemet any kind of purging expired and not used sessions in memory).
AFAIK couchdb doesn't remove deleted docs from disk and just keeps them all in db marked as deleted (for sync purpose, which isn't the case with sessions, of cause).
So question is: does couchdb-expression implement any kind of purging deleted docs from db?
Otherwise it's even worsier than with MemoryStore where just unused sessions will free memory on app restart, when couchdb will store all used and unused deleted sessions (billions possibly) forever on disk.
Any thoughts?

[tkshnwesper]

That's a good point. To add to that, updating a document would create a new document (and mark it as latest) instead of simply changing the data of the existing document.

This does seem like a problem, however CouchDB has been thoughtful to provide an API to address these worries.

I think it might be a good thing to provide the user of the couchdb-expression API a configuration setting to optionally purge old records on deletion and updates.