[SERVER-3143] Matching null against an empty array behaves differently without an index Created: 25/May/11 Updated: 29/Feb/12 Resolved: 14/Dec/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
I think the behavior with an index is correct (or at least desirable) here. > db.foo.drop() ) ) ) ) { "_id" : ObjectId("4ddd6ebe90a1203088d20f68"), "a" : [ ] } |
| Comments |
| Comment by Aaron Staple [ 14/Dec/11 ] |
|
Just came across this ticket. For |