[SERVER-16601] findAndModify should report that remove and update options conflict Created: 18/Dec/14 Updated: 23/Jan/15 Resolved: 19/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | 2.8.0-rc3 |
| Fix Version/s: | 3.0.0-rc6 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Jeremy Mikola | Assignee: | Daniel Pasette (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: |
|
||||||||
| Participants: | |||||||||
| Description |
|
In versions before 2.8.0-RC3, attempting to use update and remove at the same time in findAndModify resulted in an error when sort was specified. This validation appears to have been removed in this commit (perhaps inadvertently). With the validation removed, the remove appears to take precedence. When sort is not specified, remove always takes precedence without warning the about the conflicting options. |
| Comments |
| Comment by Githook User [ 19/Jan/15 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: |