[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: |
| Comment by auto [ 26/Apr/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| 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? |