Details
-
Task
-
Resolution: Done
-
Minor - P4
-
4.4.0, 6.0.0, 6.3, 7.0.0-rc0
-
*Location*: http://docs.mongodb.org/manual/reference/command/findAndModify/
*User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.65 Safari/537.36
*Referrer*: https://www.google.com/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: reference/command/findAndModify
*Location*: http://docs.mongodb.org/manual/reference/command/findAndModify/ *User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.65 Safari/537.36 *Referrer*: https://www.google.com/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: reference/command/findAndModify
-
1
Description
Docs say:
"The findAndModify method ignores the new option for remove operations"
But the code says something different:
if ( returnNew ) {
|
errmsg = "remove and returnNew can't co-exist";
|
return false;
|
}
|
Note: it has been like this since v2.2.
Attachments
Issue Links
- is related to
-
DOCS-4968 findAndModify no longer changes return behavior depending on if a sort was specified
-
- Closed
-