-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.9
-
Component/s: Querying
-
None
-
Query
-
ALL
-
`$ne` has very inconsistent behavior when used with arrays. This behavior also differs when using `$elemMatch`, while the `$elemMatch` docs state that with one query, the results should be identical.
- is related to
-
SERVER-36681 Change {$ne: null} semantics to be more intuitive
- Backlog
- related to
-
SERVER-27442 Positional path component in match language should not act as both an array index and a field name for a single document
- Backlog
-
SERVER-1937 $gt/$lt/$ne with scalar operand yields inconsistent matches on arrays
- Closed