Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of jchris@gmail.com designates
 209.85.222.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=n1jGjx03HlExJkg5GA3tBPzmbjkIBoVfImACV4elALol2U8PvNKVE9XOqS4qIGS9Cx
         IKXgNKU8OuQGxOy86JLN4xgeaSSosYg10hv8Zbkf2Xojbl2APayiUeVbPzdd5hR24VYM
         Viav7tNbOv33ggr+UoHA5r3tjKnEWaPF+M+FA=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1078)
Subject: Re: large attachments/huge databases ?`
From: J Chris Anderson <jchris@gmail.com>
In-Reply-To: <4BEC4F33.7060503@digitalgott.de>
Date: Thu, 13 May 2010 12:26:06 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4D26E40-B531-440F-BDE0-2AD880D02C7D@gmail.com>
References: <AANLkTimb6aZ0PY75tUYoOB1tVcooFfHwjXuQMCDjvHkt@mail.gmail.com>
 <4FD426D8-F807-4FCE-8B98-36B9B0B2C058@googlemail.com>
 <4BEBCDAB.4070708@digitalgott.de>
 <AANLkTikgHoM8publkQ1wWxMaJksZ_0OIEe43cZgFS63W@mail.gmail.com>
 <20100513160136.GB9782@seblaptop> <4BEC2A4C.4090303@digitalgott.de>
 <2C9F0F2E-F87B-4BC7-B55D-7D7A2E965428@googlemail.com>
 <4BEC43B3.8070807@digitalgott.de>
 <5625AF56-BC6C-4C4E-A675-1D47711C97B9@googlemail.com>
 <02D23147-0128-454A-87BF-169CDE6D35CF@gmail.com>
 <4BEC4F33.7060503@digitalgott.de>
To: user@couchdb.apache.org


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:
>>=20
>> =20
>>> when you need versioning, you need to implement it explicitly.
>>>   =20
>>=20
>>=20
>> 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.
>>=20
>> This has the advantage that versions will replicate together, and =
they can be manually pruned by deleting individual attachments.
>>=20
>> This should be a trivial addition to jquery.couch.js or couch.js, if =
anyone's up for hacking.
>> =20
> 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 ?
>=20

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.

Chris

> thx
>=20