couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From J Chris Anderson <>
Subject Re: large attachments/huge databases ?`
Date Thu, 13 May 2010 19:26:06 GMT

On May 13, 2010, at 12:12 PM, c.Kleinhuis wrote:

> J Chris Anderson schrieb:
>> On May 13, 2010, at 11:35 AM, Sebastian Cohnen wrote:
>>> when you need versioning, you need to implement it explicitly.
>> The simplest versioning scheme is for the client to store the string representation
of a document as served by CouchDB. While updating the document contents, the original string
representation is sent back as a new attachment.
>> This has the advantage that versions will replicate together, and they can be manually
pruned by deleting individual attachments.
>> This should be a trivial addition to jquery.couch.js or couch.js, if anyone's up
for hacking.
> i need ALL versions :D from the beginning to current version, what about saving
> previous versions as an array field containing everything but the array field for saving
the versions ?

One nice thing about attachments is that history doesn't bloat the view server memory footprint
(attachments aren't available in views).

It also takes history out of the application space, so you can pretty much "add" history to
normal applications with the attachment history method.


> thx

View raw message