Perhaps the cleanest workaround maintenance-wise is to just map the temporal column name as a computed column for your CLR property. Ugly for sure, and there's still the issue with newly generated migrations wanting to rename the temporal columns. Public override ValueTask> ReaderExecutingAsync(ĬancellationToken cancellationToken = default)Ĭommand.CommandText = command.CommandText # pragma warning restore EF1001 // Internal EF Core API usage. MakeMemberAccess( parameter, memberInfo). Add( CreateMemberAssignment( instanceVariable, toSysDatePropertyInfo, shadowPropertyBase, readValueExpression)) īlockExpressions. Add( CreateMemberAssignment( instanceVariable, fromSysDatePropertyInfo, shadowPropertyBase, readValueExpression)) Var readValueExpression = valueBufferExpression. Var shadowPropertyMemberType = typeof( DateTime) Var temporalBlockExpressions = new List() įoreach ( var shadowPropertyBase in shadowPropertiesHashSet) Var bindingInfo = new ParameterBindingInfo( Call( materializationContextExpression, MaterializationContext. Var blockExpressions = new List((( BlockExpression) baseExpression). Var shadowPropertiesHashSet = new HashSet(ĮntityType. Var fromSysDatePropertyInfo = entityType. FirstOrDefault( i => i = typeof( ITemporalEntity)) != null) CreateMaterializeExpression( entityType, entityInstanceName, materializationContextExpression) Public override Expression CreateMaterializeExpression( IEntityType entityType, string entityInstanceName, Expression materializationContextExpression) Public TemporalEntityMaterializerSource( EntityMaterializerSourceDependencies dependencies) : base( dependencies)

public class TemporalEntityMaterializerSource : EntityMaterializerSource, Microsoft. # pragma warning disable EF1001 // Internal EF Core API usage.

Ah shadow complex map