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
When we query for DerivedEntity, we will lose MyProperty property values. This is because the backing field of the base class is used, rather than the backing field of the derived class. Fluent api also does't work:
ajcvickers
changed the title
Limitation: Can not individually configure overridden properties of derived entity classes
Limitation: Properties are limited to a single backing field
Feb 1, 2021
@anranruye Thanks for reporting this. I'm putting this on the backlog for now, but this will be non-trivial to implement and so we are only likely to do so we significantly more feedback indicating that this is important. You can instead access the property through its navigation which will produce the correct results.
AndriySvyryd
changed the title
Limitation: Properties are limited to a single backing field
Allow properties to use a different backing field on a derived type
Jan 14, 2022
EF Core version: 5.0.2
Database provider: Microsoft.EntityFrameworkCore.SqlServer
Target framework: .NET 5.0
Operating system: Windows 7
IDE: Visual Studio 2019 16.8
Consider we have the following entities:
When we query for
DerivedEntity
, we will loseMyProperty
property values. This is because the backing field of the base class is used, rather than the backing field of the derived class. Fluent api also does't work:A workaround is to use same backing field for both base and derived classes. However, it's not always possible to change the base class.
I don't know whether this is a by-design/known limitation. I don't find this in the pages:
https://docs.microsoft.com/en-us/ef/core/modeling/inheritance
https://docs.microsoft.com/en-us/ef/core/modeling/backing-field.
The text was updated successfully, but these errors were encountered: