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: <48C58B7F-CF5E-4A3E-8C93-ED20DD3C68EE@couchbase.com>
References: 
 <CAL-h1aR9Vye0zuiLY7ihMxBs7B4trE1Gew=2XHhj_Bfv8Fj6Eg@mail.gmail.com>
	<CAN-3CBKb2BvDf9DzRLw_G=hEKZKw_TVF-F19W9Hq=SbyDM5i+w@mail.gmail.com>
	<CAL-h1aSM7LVV7t0QSqSkQz5oaLoHDGODwK8VC3n2LjGYQjR9Wg@mail.gmail.com>
	<48C58B7F-CF5E-4A3E-8C93-ED20DD3C68EE@couchbase.com>
Date: Mon, 22 Aug 2011 09:49:09 +0100
Message-ID: 
 <CABvT1DER9STB9E_UF1G+iAA-LJT_d2J1EEiQWB49ZT=P7_+nDg@mail.gmail.com>
Subject: Re: What's the best way to jack up the rev number?
From: Robert Newson <rnewson@apache.org>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Ryan,

As others have noted, you don't need to bump the 'number on the front'
to 'force' updates. Just update the document and replicate. If the
change isn't appearing on the target then the document has conflicting
revisions and your new update was one of the losers. Delete the
revisions *you* deem the losers, and it'll pop right up.

I confess to not finding illumination in comparisons between CouchDB
and Git, any analogy there tends to falls down at exactly the point
where the differences are important.

B.

On 22 August 2011 06:24, Jens Alfke <jens@couchbase.com> wrote:
>
> On Aug 21, 2011, at 10:04 PM, Ryan Ramage wrote:
>
> A summary from the link....I have a master couchapp that clients pull
> replicate from. A refactoring of the couchapp may mess up the rev number =
for
> the main design doc. So i need a way to go past the rev number to force a=
n
> update to the clients. Is there a better way?
>
> The revision IDs aren=92t =93numbers=94 (again, just like Git). They do h=
appen to have incrementing digits at the start, before the hashcode, but I=
=92m told that=92s just a detail of the implementation and shouldn=92t be r=
elied on. In the general case there isn=92t any way to put an ordering on r=
evisions, since different peers can be creating them out of contact with ea=
ch other and then merging, so the replication algorithm doesn=92t pay any a=
ttention to those digits at the beginning.
>
> =97Jens
>