-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
-
QE 2021-08-23, QE 2021-09-06, QE 2021-09-20, QE 2021-10-04
-
153
$ifNull behaves differently in latest when the replacement value is null. In earlier versions it returned null. In latest it omits the field entirely.
While it may sound silly to use a replacement value of null, the LINQ provider in the C# driver uses this construct to replace a missing field with an explicit null-valued field.
- is caused by
-
SERVER-55295 Short circuit $ifNull expression if the condition always evaluates to a constant or null
- Closed
- is depended on by
-
CSHARP-3726 Fix GroupJoin_syntax_with_select_many_and_DefaultIfEmpty failure on latest
- Closed