-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Minor - P4
-
None
-
Affects Version/s: 2.0.6, 2.3.2
-
Component/s: Querying
-
None
-
Environment:Linux
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Some code to reproduce bug:
> db.geo.insert(
{coords:[0,1], field: 1})
> db.geo.insert(
)
> db.geo.insert(
)
> db.geo.ensureIndex(
)
Then:
> db.geo.find({coords : {$near:[1,1]}})
{ "_id" : ObjectId("4fe1e02e033df621f3c59861"), "coords" : [ 0, 1 ], "field" : 1 } { "_id" : ObjectId("4fe1e037033df621f3c59862"), "coords" : [ 2.3, 1.4 ], "field" : 2 } { "_id" : ObjectId("4fe1e03f033df621f3c59863"), "coords" : [ 1, 5 ], "field" : 0 }Seems ok!
> db.geo.find({coords : {$near:[1,1]}}).skip(1)
Bug?
> db.geo.find({coords : {$near:[1,1]}}).skip(1).limit(1)
{ "_id" : ObjectId("4fe1e037033df621f3c59862"), "coords" : [ 2.3, 1.4 ], "field" : 2 }?!
Btw my php code doesn't work with limit() setted.
- duplicates
-
SERVER-5390 geo query with explicit skip and no explicit limit returns no results
-
- Closed
-