[DOCS-7904] Enhance replaceOne() documentation on upsert behavior Created: 18/May/16 Updated: 11/Jan/17 Resolved: 22/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Ramon Fernandez Marina | Assignee: | Jonathan DeStefano |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 29 weeks, 5 days ago | ||||||||
| Description |
|
The findAndModify() documentation reads, on the upsert option:
IIUC, replaceOne has the same behavior, but we don't warn about the need for unique indexes when upsert is set to true. This ticket is to suggest adding the quoted paragraph above to the replaceOne() documentation. |
| Comments |
| Comment by Githook User [ 22/Jul/16 ] |
|
Author: {u'username': u'jdestefano-mongo', u'name': u'jonathan', u'email': u'jonathan.destefano@10gen.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |