[SERVER-7264] numeric mod prevents application of positional mod on same field, without uassert Created: 04/Oct/12 Updated: 11/Jul/16 Resolved: 27/Jul/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
If an explicit array field mod and a positional mod reference the same field, the numeric mod currently wins out. Generally when (non positional) mods may conflict we uassert instead of allowing one to trump the other. We might consider adopting a policy that is similar to that. Test:
|
| Comments |
| Comment by Scott Hernandez (Inactive) [ 27/Jul/13 ] | ||||||
|
Fixed in In the new update code this fails:
|