You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The callbacks in IMaterializationInterceptor occur on an entity-by-entity basis without any consideration of related entities. For example, on materialization I cannot validate or calculate something that requires a related entity (always included in my queries).
It would be useful to have a materialization interceptor method that is called with an enumerable of the materialized entities after they have been identity-resolved and navigations have been populated. Alternatively, a DbContext event for this.
Commenting that the entities in the enumerable may not be tracked, if tracking was disabled for the query.
The text was updated successfully, but these errors were encountered:
The callbacks in IMaterializationInterceptor occur on an entity-by-entity basis without any consideration of related entities. For example, on materialization I cannot validate or calculate something that requires a related entity (always included in my queries).
It would be useful to have a materialization interceptor method that is called with an enumerable of the materialized entities after they have been identity-resolved and navigations have been populated. Alternatively, a DbContext event for this.
Commenting that the entities in the enumerable may not be tracked, if tracking was disabled for the query.
The text was updated successfully, but these errors were encountered: