-
Notifications
You must be signed in to change notification settings - Fork 2k
Please clarify "inheritance hierarchy" limitation #1239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I've tested this in EFCore 2.2. |
This works because the owned types are mapped to a different table? Have you tried seeding data to the inherited member? have you tried doing table splitting instead of a different table? I tried and did not work for me... would like to know if I'm doing something wrong |
@laguer71 Those scenarios are supported. If you are getting errors create and issue on https://github.com/aspnet/EntityFrameworkCore/issues with a small repro project, preferably targeting 3.0.0 |
@laguser71 Agree with above comment. Before creating issue on Github, you can also check for my blogs for more detail example. It is about using table split & owned types together. But sorry, they are in Chinese, but the source code and screen shots are all English. So just scroll the source code & screen part is enough. The URLs are: https://www.cnblogs.com/fatkent/p/10436274.html & https://www.cnblogs.com/fatkent/p/10436991.html |
This article states:
> Current shortcomings
> Inheritance hierarchies that include owned entity types are not supported
I interpreted this to mean that entities that are in an inheritance hierarchy cannot include owned entities. But, according to this GitHub discussion the limitation means that the owned entities themselves cannot be part of an inheritance hierarchy. Please clarify this detail.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: