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 zachary.zolton@gmail.com
 designates 209.85.218.218 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=LvzkNWvR4Jf+M8XvRUoE9m5Vc953ydThA/ckLF4v+rMW+y5rE6GDgwwvC6ooyE71N+
         KPEhvfpDHX6G2nq+IwiKUfhpWH43tkHvGu1qmUgEx91czXHGZLw4JoQvg4K7LOyZ/Wvw
         Ys7El2RNwOOpQwookqbS2JLpn9mv5JT3UXPVY=
MIME-Version: 1.0
In-Reply-To: <e8d26ac40906090833h257bf9f6h5f11847057d7a60c@mail.gmail.com>
References: <e8d26ac40906090833h257bf9f6h5f11847057d7a60c@mail.gmail.com>
From: Zachary Zolton <zachary.zolton@gmail.com>
Date: Tue, 9 Jun 2009 10:47:06 -0500
Message-ID: <f728979f0906090847o671e806en44254c1aa58f1813@mail.gmail.com>
Subject: Re: document revisions
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=001485f6cd0682a58d046bec465d

--001485f6cd0682a58d046bec465d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

You'll want to model your documents in terms of revisions.
For some ideas, see approaches 3 and 4 on this wiki page:
http://wiki.apache.org/couchdb/How_to_design_for_replication

On Tue, Jun 9, 2009 at 10:33 AM, Adam Wolff <awolff@gmail.com> wrote:

> Hi everyone,Our app needs to preserve document revisions. I know that the
> revision feature of couchdb is not intended for application-level document
> revisions, but the semantics of couch's revisions are perfect for our app,
> and I don't want to have to rebuild that feature. What's the best way to
> take advantage of couch's built-in revisions? I know we can't rely on the
> revisions being there, but they *are* there right after you write a new
> version. After a successful write, the caller could be responsible for
> putting a separate document for the old revision, right?
>
> Alternatively, is this a mod to couchdb that we should explore? A feature
> so
> that you can say: for the documents in this database, preserve the
> revisions
> even upon compaction.
>
> Thoughts? Thanks,
> A
>

--001485f6cd0682a58d046bec465d--