[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: SERVER-1705 validate op type with regex
http://github.com/mongodb/mongo/commit/30c59fa55079088d1d60a318e5e3f526f600856e

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.

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