Dear Wiki user, You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change 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=diff&rev1=8&rev2=9 -------------------------------------------------- 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 have
