[SERVER-1005] $not/$or Created: 12/Apr/10  Updated: 02/Aug/18  Resolved: 26/Apr/10

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 1.5.1

Type: Task Priority: Major - P3
Reporter: Aaron Staple Assignee: Gregory McKeon (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Comments   
Comment by auto [ 26/Apr/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-1005 more correct error messages
http://github.com/mongodb/mongo/commit/ccb496081ec1bbe05ea8e0e9e8d9c7ac59f5e7b5

Comment by auto [ 26/Apr/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-1005 $nor
http://github.com/mongodb/mongo/commit/51daf493a177247bfd065956d69dc6aa853ca1dd

Comment by Aaron Staple [ 13/Apr/10 ]

So right now $not only applies within a field, eg {a:{$not:/a/}}. This syntax isn't great for $or. Should I just add $nor, which would need to be a top level field the same way $or must be?

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