-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Complete the sample with the typed discriminator mapping #4322
Conversation
The sample is missing a `HasValue` statement, which actually does the mapping. The `HasValue` statement is available for the sample with shadow-mappings.
@eluchsinger The call to @AndriySvyryd In the actual code sample, the subtype is not mapped. One way to map it would be to have |
Yep. |
samples/core/Modeling/Inheritance/FluentAPI/NonShadowDiscriminator.cs
Outdated
Show resolved
Hide resolved
samples/core/Modeling/Inheritance/FluentAPI/NonShadowDiscriminator.cs
Outdated
Show resolved
Hide resolved
samples/core/Modeling/Inheritance/FluentAPI/NonShadowDiscriminator.cs
Outdated
Show resolved
Hide resolved
samples/core/Modeling/Inheritance/FluentAPI/NonShadowDiscriminator.cs
Outdated
Show resolved
Hide resolved
samples/core/Modeling/Inheritance/FluentAPI/NonShadowDiscriminator.cs
Outdated
Show resolved
Hide resolved
Thanks! |
The sample is missing a
HasValue
statement, which actually does the mapping. TheHasValue
statement is available for the sample with shadow mappings.These docs will be changed by this PR: Inheritance - Table per Hierarchy And Discriminator Configuration
This other sample using untyped mappings for the discriminator is using the
HasValue
statement correctly: Sample with shadow mappings