Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: <92E0C47B-2734-43B9-93CE-52B75A2C7C67@couchbase.com>
References: <1D83CDC2-5CD1-44D0-AC2B-5FE7D0614AF8@mooseyard.com>
	<CAJ_m3YBTi4BJb_Kuer6--P=DtE6hXO42Su63zi9_OtD8B=vGkg@mail.gmail.com>
	<92E0C47B-2734-43B9-93CE-52B75A2C7C67@couchbase.com>
Date: Wed, 13 Jul 2011 00:34:27 +0100
Message-ID: 
 <CABvT1DFD9N2pBFdqSmKieEYt7=5WJiZ7N5CwnL3YaKmipiVeiw@mail.gmail.com>
Subject: Re: Is it OK to interpret the generation count in a revision ID?
From: Robert Newson <rnewson@apache.org>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

The wiki does mention it (though I'll point out politely that the
couchbase docs, while lovely, are not official atm).

The rev values should be treated opaquely, we don't promise not to
change the format. The contents of the conflicts is what you are
supposed to use to resolve them, just as you do in source code (you
don't use the revision id directly in SVN, right?).

B.

On 13 July 2011 00:11, Jens Alfke <jens@couchbase.com> wrote:
>
> On Jul 12, 2011, at 2:54 PM, Paul Davis wrote:
>
> In this particular case, I'm not sure if we even document that the
> revs=3Dtrue option exists, as I can't think of where it would be used
> outside the replicator so even the format of this response might be
> subject to change.
>
> No, it=92s well documented both in the CouchDB wiki and in Couchbase=92s =
API docs:
>
> http://wiki.apache.org/couchdb/HTTP_Document_API#GET
> http://www.couchbase.org/sites/default/files/uploads/all/documentation/co=
uchbase-api-dbdoc.html#couchbase-api-dbdoc_db-doc_get-revs
>
> So is the =91extended revision history=92, ?revs_info=3Dtrue.
>
> Not sure why the revision history would be viewed as internal, as it=92s =
pretty important for conflict resolution.
>
> =97Jens
>