From e3b18946a0840ab271e8ec096d5f7a2c1ff533a8 Mon Sep 17 00:00:00 2001 From: Naomi Pentrel <5212232+npentrel@users.noreply.github.com> Date: Tue, 23 Mar 2021 13:12:34 +0100 Subject: [PATCH] DOCS-13725 update cursor snapshot documentation --- .../extracts-concurrency-consistency-recency.yaml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source/includes/extracts-concurrency-consistency-recency.yaml b/source/includes/extracts-concurrency-consistency-recency.yaml index 6b551f0d860..a67374cc505 100644 --- a/source/includes/extracts-concurrency-consistency-recency.yaml +++ b/source/includes/extracts-concurrency-consistency-recency.yaml @@ -106,12 +106,12 @@ content: | change the indexed field on the index used by the query; then the cursor will return the same document more than once. - If your collection has a field or fields that are - never modified, you can use a *unique* index on this field or these - fields so that the query will return each document no more than - once. Query with :method:`~cursor.hint()` to explicitly force the - query to use that index. - + Queries that use :ref:`unique indexes ` can, in + some cases, return duplicate values. If a cursor using a unique index + interleaves with a delete and insert of documents sharing the same + unique value, the cursor may return the same unique value twice from + different documents. + --- ref: lock-general content: |