-
Type: Improvement
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Querying
-
None
If we have {a:{$gt:"a",$lt:"r",$not:/^f/}} we'll still scan the strings beginning with f.
- depends on
-
SERVER-667 implement tightest btree bounds possible for $not expressions
- Closed
-
SERVER-1211 don't use simplifiedQuery() to negate earlier index ranges in new matcher
- Closed
- is depended on by
-
SERVER-1213 allow splitting new $or range in two
- Closed
- is related to
-
SERVER-7261 field range with $not should properly account for type bracketing (query with $not returns different results after adding an index)
- Closed