[SERVER-27371] Need Option to Set Null Semantics Created: 12/Dec/16 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Bryan Reinero | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Participants: |
| Description |
|
In SQL NULL is not a value, which means that any comparison to NULL is false, even if both sides are NULL. In MongoDB, however, null is considered a value. It would be helpful to have an aggregation option to set SQL null semantics, where fields that are either NULL, undefined, or missing return false when compared to NULL. |
| Comments |
| Comment by Asya Kamsky [ 21/Dec/16 ] |
|
In addition, in MongoDB language, when a field is missing, sometimes it's considered equal/equivalent to the value being null. Aggregation framework in particular has a concept of "null-ish" values which are treated the same way in some contexts. |