Mailing-List: contact commits-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Sun, 01 Nov 2009 22:08:43 -0000
Message-ID: <20091101220843.12749.49757@eos.apache.org>
Subject: 
 =?utf-8?q?=5BCouchdb_Wiki=5D_Update_of_=22Replication=5Fand=5Fconflicts?=
 =?utf-8?q?=22_by_BrianCandler?=

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for c=
hange notification.

The "Replication_and_conflicts" page has been changed by BrianCandler.
The comment on this change is: all_or_nothing transaction boundaries *aren'=
t* preserved through replication.
http://wiki.apache.org/couchdb/Replication_and_conflicts?action=3Ddiff&rev1=
=3D8&rev2=3D9

--------------------------------------------------

  the changes in the request will be forcibly applied to the database, even=
 if
  that introduces conflicts.  The only guarantee you are given is that they
  will either all be applied to the database, or none of them (e.g.  if the
- power is pulled out before the update is finished writing to disk). They
+ power is pulled out before the update is finished writing to disk).
- also replicate together as an atomic unit.
  =

  So this gives you a way to introduce conflicts within a single database
  instance.  If you choose to do this instead of PUT, it means you don't ha=
ve