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 rhiebert@puc.edu designates
 65.54.190.162 as permitted sender)
From: Ryan D Hiebert <rhiebert@puc.edu>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Subject: Replication Order
Thread-Topic: Replication Order
Thread-Index: AQHMFaybDK5wrgOH8EGdrPuzuigenA==
Date: Wed, 18 May 2011 22:40:38 +0000
Message-ID: <D215EDC5-B56E-499F-A89C-79B9B298E9BA@puc.edu>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-ID: <99DBBE65CE6AF24686171649B43B0116@namprd02.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

When replication is being done, in what order will the changes be applied? =
 In the order that they happened, or in the order of the _id they refer to,=
 or some other ordering, or is there no ordering that can be expected.  For=
 instance, if I move a document, I would like to make sure that I never hav=
e two versions of the document.  To this end, I first delete the document, =
and then create it again with the new _id.  In a replicated database, can I=
 be sure that the document will be first deleted, and then created on the r=
eplicated database?

Thanks,

Ryan=