[SERVER-10302] Use new update framework to enforce presence of _id in upserts Created: 23/Jul/13 Updated: 02/Aug/18 Resolved: 26/Jul/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Gregory McKeon (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
If a new document is generated as a result of an upsert, make sure that such document would contain an _id field. |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 26/Jul/13 ] |
|
jstests/upsert1.js tests this and is passing. |