[SERVER-7452] Add an upsert flag to the applyOps command Created: 23/Oct/12 Updated: 31/Jul/17 Resolved: 30/Oct/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | 2.3.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Steve Briskin (Inactive) | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Add a flag to the applyOps command to control whether updates are treated as updates or upserts. |
| Comments |
| Comment by auto [ 12/Feb/13 ] | |
|
Author: {u'date': u'2013-01-02T16:47:52Z', u'name': u'Steve Briskin', u'email': u'steve.briskin@10gen.com'}Message: Signed-off-by: Ian Whalen <ian.whalen@gmail.com> | |
| Comment by Randolph Tan [ 30/Oct/12 ] | |
|
All updates are now treated as upsert in applyOps unless passed with alwaysUpsert: false. Ex:
| |
| Comment by auto [ 30/Oct/12 ] | |
|
Author: {u'date': u'2012-10-29T13:58:18-07:00', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |