Arthur Vickers
Arthur Vickers
@Steve887 Do you see the same behavior if you change the query to be no-tracking? For example: ```C# return await _context.Set() .Include(x => x.ConsultationViews).ThenInclude(x => x.ConsultationItems).ThenInclude(x => x.Item) .AsNoTracking() .FirstOrDefaultAsync(p...
@MarkGodwin Value conversions are not translated to SQL--that feature is tracked by #10861. Instead, the value is read from the database and then converted. This is because the primary purpose...
@Skulblaka Yes.
See also #22542
Note for implementation: consider the case where the value converter changes the type from nullable to non-nullable, or vice versa. See #24534.
@BickelLukas The ability of value converters to change the nullability of columns is tracked by #24685. I haven't been able to find a workaround for this case. Beyond that, value...
For anyone watching this issue: there are significant problems when executing queries that either convert nulls in the database to non-nulls in code or vice-versa. Therefore, we have marked this...
@douglasg14b The API hasn't changed, it's just marked as internal because converting nulls only works correctly in very limited cases. This is because the database, .NET, and EF Core all...
@chris-pie In the general case, this is a very involved fix that requires understanding how the query pipeline handles nulls and null semantics. Realistically, this would be a big, complex...
Notes from team meeting: I was thinking about this again following investigation of #35051 and I think the cases where nulls have special behavior--for example, when used in a PK...