Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of robert.newson@gmail.com
 designates 209.85.214.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=wBeFherpajU/BgDA1XseL/+TRgMd3j3EhhiXAZnVEdczlxUynGzwDIPbDQQvwvjctn
         oBXyWFtYkVYr+P23+0xZXXR1lZ1+ZrROB71eHT5+wJmuXd4WByhyApKmNPpfucKxmPBe
         BR5W4S1oVMHkeBS7Sv3TT2nMAkjV8ZTMA05iE=
MIME-Version: 1.0
In-Reply-To: <1302338725.29780.6.camel@otto.amantes>
References: <1302198233.3064.15.camel@ana.amantes>
	<BANLkTimXZPQNmvunkQUWfYx8bqU_39HotQ@mail.gmail.com>
	<1302338725.29780.6.camel@otto.amantes>
Date: Sat, 9 Apr 2011 10:42:31 +0100
Message-ID: <BANLkTinrmYFJ+vdDzmvzSFOV6+n7MxVY1Q@mail.gmail.com>
Subject: Re: change notifications question
From: Robert Newson <robert.newson@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

CouchDB does not provide revisioning or history features to the end
user at all. This is a common mistake.

The use of _rev and MVCC is purely a mechanism to enable sane
replication between servers where writes are permitted everywhere.
CouchDB's replication will only ensure that the current version* of
any document is replicated, earlier revisions are *not* replicated.
Earlier revisions are also removed on compaction, which is an
essential maintenance operation.

B.

* Strictly, CouchDB replicates all leaf revisions of all documents,
the difference is only noticeable if a document has conflicts (all
conflicting versions will be replicated).

On 9 April 2011 09:45, Thomas Vander Stichele <svsamoht@gmail.com> wrote:
> On Thu, 2011-04-07 at 11:19 -0700, Mark Hahn wrote:
>> You are not even guaranteed the old version will be there.
>
> I would be ok with that, it doesn't seem to be a big problem in
> practice. =A0(Although it's strange to me that all the infrastructure is
> there to have document revisions, but we have no control over how much
> history we want couchdb to keep. =A0Seems like a relatively
> straightforward next step).
>
>> =A0 You need
>> to build history into your app.
>
> Can you be a bit more explicit about what you mean?
>
> It sounds like you say I should re-write CouchDB's revisioning/history
> approach in my app just to get around the fact that couchdb has no
> controls for history. =A0I might as well build it on top of anything else
> than couchdb no ? :)
>
> Thanks
> Thomas
>
>
>