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 svsamoht@gmail.com designates
 74.125.82.42 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:from:to:cc:in-reply-to:references:content-type:date
         :message-id:mime-version:x-mailer:content-transfer-encoding;
        b=AqnBa7/S5zUqZ0+h/OCDfJKDM/eUEFt9AVlmwyThw+79Mikfr2kAWWI8ke+9lkuWE2
         FEzK/f2fNQNblBsgJXXxF/VNrKqIXC3MnyGMAjIOf92Ke9iCeIS44xQGN7jCFq7McMQz
         QcU+pIZVFbu/iY0kOrO3GwjBH2gBBWoM+Xbyo=
Subject: Re: change notifications question
From: Thomas Vander Stichele <svsamoht@gmail.com>
To: Mark Hahn <mark@boutiquing.com>
Cc: user@couchdb.apache.org
In-Reply-To: <BANLkTimXZPQNmvunkQUWfYx8bqU_39HotQ@mail.gmail.com>
References: <1302198233.3064.15.camel@ana.amantes>
	 <BANLkTimXZPQNmvunkQUWfYx8bqU_39HotQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Sat, 09 Apr 2011 10:45:25 +0200
Message-ID: <1302338725.29780.6.camel@otto.amantes>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

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.  (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.  Seems like a relatively
straightforward next step).

>   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.  I might as well build it on top of anything else
than couchdb no ? :)

Thanks
Thomas