[SERVER-1212] tighter index bounds for negated regular expression Created: 10/Jun/10 Updated: 15/Jun/15 Resolved: 15/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | David Storch |
| Resolution: | Won't Fix | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
If we have {a:{$gt:"a",$lt:"r",$not:/^f/}} we'll still scan the strings beginning with f. |
| Comments |
| Comment by David Storch [ 15/Jun/15 ] |
|
We currently do not have plans to change how we index negated regular expression predicates. Closing as "Won't Fix". |
| Comment by Aaron Staple [ 31/Aug/10 ] |
|
I had intended for this bug to cover all sorts of negated ranges, including $ne and $not ranges. I also created I've done $ne and will be working on $nin next. |
| Comment by auto [ 30/Aug/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by auto [ 30/Aug/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |