From 26f494353b9f90e57b3a8f21db35b95c7d88c1e7 Mon Sep 17 00:00:00 2001 From: Kyle Suarez Date: Wed, 13 Jan 2016 15:19:36 -0500 Subject: [PATCH] DOCS-6971 findAndModify + write concern error The comparison between findAndModify with the update command erroneously stated that the former does not take a write concern. A write concern can be specified starting in MongoDB 3.2. --- source/includes/fact-findAndModify-update-comparison.rst | 5 ----- 1 file changed, 5 deletions(-) diff --git a/source/includes/fact-findAndModify-update-comparison.rst b/source/includes/fact-findAndModify-update-comparison.rst index c455c7cb537..c0c9f376df6 100644 --- a/source/includes/fact-findAndModify-update-comparison.rst +++ b/source/includes/fact-findAndModify-update-comparison.rst @@ -24,11 +24,6 @@ When updating a document, |operation| and the only a single document but multiple documents matched, you will need to use additional logic to identify the updated document. -- You cannot specify a :doc:`write concern ` to - |operation| to override the default write concern whereas, starting - in MongoDB 2.6, you can specify a write concern to the - :method:`~db.collection.update()` method. - When modifying a *single* document, both |operation| and the :method:`~db.collection.update()` method *atomically* update the document. See :doc:`/core/write-operations-atomicity` for more