- 
    Type:Bug 
- 
    Resolution: Done
- 
    Priority:Major - P3 
- 
    Affects Version/s: 1.5.2
- 
    Component/s: Querying
- 
        Minor Change
- 
        ALL
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
Here a test-case:
> db.test.insert({"field": [[100,300],[100, 110]]}) 
> db.test.findOne() 
{ 
        "_id" : ObjectId("4c1f229882c620b16f0d3fbd"), 
        "field" : [ 
                [ 
                        100, 
                        300 
                ], 
                [ 
                        100, 
                        110 
                ] 
        ] 
}
These two commands should find this element but they don't:
> db.test.find({"field": {$elemMatch: {0: 100, 1:300}}}) 
> db.test.find({"field": {$elemMatch: {0: {$gt: 1}, 1: {$gt: 1}}}}) 
- depends on
- 
                    SERVER-6613 using $elemMatch projection with $all gives unexpected results -         
- Closed
 
-         
- is depended on by
- 
                    CSHARP-611 Support for Enumerable.Any in LINQ queries for StringSerializer like List<string> Properties -         
- Closed
 
-         
- is related to
- 
                    SERVER-15727 two-dimension Array $elemMatch bug -         
- Closed
 
-         
- 
                    SERVER-5506 Enhance SERVER-1264 style $elemMatch functionality so that all mongo operators/functionality are supported -         
- Backlog
 
-         
- related to
- 
                    SERVER-7388 Implement all query operators using MatchExpression -         
- Closed
 
-         
- 
                    SERVER-6050 Consider allowing $elemMatch applied to non arrays -         
- Closed
 
-