[SERVER-251] no way to negate regex (WAS: doesn't work with $ne) Created: 24/Aug/09 Updated: 12/Jul/16 Resolved: 23/Feb/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.3 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Eliot Horowitz (Inactive) | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 7 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
jstests/regex4.js |
| Comments |
| Comment by Aaron Staple [ 23/Feb/10 ] |
|
Theoretically when we $not a very simple regex (so simple that we don't actually need pcre for the match) we could calculate a set of index bounds on either side of the regex match range...not going to implement this unless requested. |
| Comment by auto [ 23/Feb/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by Eliot Horowitz (Inactive) [ 23/Feb/10 ] |
|
i think just BSON regex |
| Comment by Aaron Staple [ 22/Feb/10 ] |
|
Does $not need to support the $regex/$options syntax, or is it sufficient to handle regex BSON elements? |
| Comment by Eliot Horowitz (Inactive) [ 10/Sep/09 ] |
|
not a sub-task but dependant on |