[SERVER-1932] range queries on arrays behave inconsistently without indexes Created: 12/Oct/10  Updated: 12/Jul/16  Resolved: 01/Apr/11

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: None
Fix Version/s: 1.9.0

Type: Bug Priority: Major - P3
Reporter: Aaron Staple Assignee: Aaron Staple
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-958 Range queries on arrays behave differ... Closed
Operating System: ALL
Participants:

 Description   

> db.f.drop();
true
> db.f.save(

{ a:[1,10] }

);
> db.f.find( { a:

{ $gt:2,$lt:5}

} );

{ "_id" : ObjectId("4cb4dbd632dad83b4dd8a524"), "a" : [ 1, 10 ] }

> db.f.find( { a:

{ $gt:5,$lt:2}

} );
>



 Comments   
Comment by auto [ 31/Mar/11 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-1932 Don't check invalid field range with table scan
Branch: master
https://github.com/mongodb/mongo/commit/86ae5d6fd99138d02f3a7a15e388e77c683e8983

Generated at Thu Feb 08 02:58:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.