all_or_nothing doesn't introduces conflicts. It allows CouchDB to return an error response if any write fail. For introducing conflicts, use new_edits: false. But this is not a force write as validate_doc_update still may block your writes. -- ,,,^..^,,,
On Thu, May 14, 2015 at 4:38 PM, Peter Norwich <[email protected]> wrote: > Is bulk_docs' all_or_nothing going to be supported in 2.0 ? > I see dev preview says "not supported yet". > > If not, what will be the new way of introducing conflict in 2.0 ? Is there a > 'force write' flag during PUT ? > I just need a way to always write successfully. > > My use case: > - offline client, will upload the doc when online > - server saves doc, return winning rev and conflict info to client > - client can fetch all conflicts and manually resolve them > > Thanks :) > Peter
