Skip to content
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

Pull down relationship to the derived type when setting a navigation targeting the derived type. #16872

Merged
merged 1 commit into from
Jul 31, 2019

Conversation

AndriySvyryd
Copy link
Member

Remove ambiguous navigations when the target type is ignored or a base type is set that has the navigation ignored.
Throw correct exception when the collection navigation type doesn't match the dependent entity type.

Fixes #16762

@AndriySvyryd AndriySvyryd requested a review from smitpatel July 31, 2019 18:08
…targeting the derived type.

Remove ambiguous navigations when the target type is ignored or a base type is set that has the navigation ignored.
Throw correct exception when the collection navigation type doesn't match the dependent entity type.

Fixes #16762
Copy link
Contributor

@smitpatel smitpatel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@AndriySvyryd AndriySvyryd merged commit cf4e8ce into release/3.0 Jul 31, 2019
@ghost ghost deleted the DerivedNavigations branch July 31, 2019 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Changing a DbSet<> property name can create incorrect TPH foreign keys in model
2 participants