The wiki is wrong (rather, reflects ancient all_or_nothing:true behavior). The atomicity was removed because it will break when databases are sharded (ala bigcouch), it violated the principle that a single couchdb node and a couchdb cluster should behave the same way.
On 19 December 2012 02:02, Jens Alfke <[email protected]> wrote: > >> On Tue, Dec 18, 2012 at 11:58 PM, Robert Newson <[email protected]> >> wrote: >>> I'll also note that there's no atomicity to a _bulk_docs request (even >>> with all_or_nothing:true) except at the individual document level (as >>> usual). > > Really? The wiki documentation implies atomic behavior — either all the docs > are written or none are. And I assume they’re written in one update of the > database file (it would be really inefficient otherwise) so any reader will > either see the state before the docs were written, or the one afterwards. > > —Jens
