InMemory: Server side null safety does not work always

[smitpatel]

            var actual = context.Set<DateTimeEnclosure>()
                .Select(e => new { DT = e.DateTimeOffset == null ? (DateTime?)null : e.DateTimeOffset.Value.DateTime.Date }).ToList();

We translate the whole thing to server side but we do .Value over Nullable<DateTimeOffset> which throws with null value.

Test: Optional_datetime_reading_null_from_database

[smitpatel]

Closing this as by design.
InMemory server side throws more exception than other providers because it can. This is a case where InMemory server side does throw an exception and we cannot change the behavior trivially. If there is real customer issue arising from this behavior then we will look into it.