[SERVER-1737] upsert doesn't create new obj correctly with array criteria Created: 05/Sep/10 Updated: 17/Mar/11 Resolved: 10/Sep/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kristina Chodorow (Inactive) | 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 you do an upsert with an array as the criteria, the criteria isn't included in the new obj: > db.foo.update( {x:[5,6]}, {y:2},true) |
| Comments |
| Comment by Kristina Chodorow (Inactive) [ 10/Sep/10 ] |
|
Whoops. |