[SERVER-1705] $ne with regex Created: 31/Aug/10 Updated: 12/Jul/16 Resolved: 31/Aug/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.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 | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
$ne doesn't work correctly with a regex (and matching behavior is different depending on whether an index is used). Should we make $ne + regex behave the same as $not + regex, or should we prevent people from using $ne with regex? |
| Comments |
| Comment by auto [ 31/Aug/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by Eliot Horowitz (Inactive) [ 31/Aug/10 ] |
|
Ok |
| Comment by Aaron Staple [ 31/Aug/10 ] |
|
Sounds good, if it's ok with you I'll make sure we uassert when someone attempts this. Right now it's just returning weird results. |
| Comment by Eliot Horowitz (Inactive) [ 31/Aug/10 ] |
|
I think $ne with regex is weird - so we shouldn't support. |