-
Notifications
You must be signed in to change notification settings - Fork 1.7k
improvements to findAndModify/db.collection.findAndModify ref #2078
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@@ -117,19 +116,22 @@ multiple clients issue the following command: | |||
|
|||
If all the commands finish the ``query`` phase before any command | |||
starts the ``modify`` phase, **and** there is no unique index on the | |||
``name`` field, the commands may all result in an insert. To prevent | |||
``name`` field, the commands may all perform an upsert, creating |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/all/each/
My notes in, otherwise LGTM. |
field, the commands may all perform an upsert, creating | ||
multiple duplicate documents. | ||
|
||
To prevent this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
replace "this condition" with the condition, given that its in its own paragraph now
lgtm modulo comments |
Merged, with Sam & Michael's feedback. |
…ial in v6.0 (#2069) (#2078) * DOCSP-25533 removes incorrect statement from "Clear Jumbo Flag" tutorial * internal review feedback
Co-authored-by: Oleg Pudeyev <[email protected]>
No description provided.