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

Configure the correct end as principal for self-ref collection with [ForeignKey] #26372

Merged
merged 1 commit into from
Oct 18, 2021

Conversation

AndriySvyryd
Copy link
Member

Fixes #26364

Description

Using [ForeignKey] on a self-ref collection navigation results in an exception during model building.

Customer impact

The exception is thrown from a convention that runs before Fluent API configuration. The only reasonable workaround is to remove the [ForeignKey].

How found

Multiple customer reports on RC2.

Regression

Yes, from 6.0 RC1, introduced in #25806

Testing

Test for this scenario added in the PR.

Risk

Low, the changed code only affects self-ref navigations with [ForeignKey].

@AndriySvyryd AndriySvyryd changed the title [6.0] Configure the correct end as principal for self-ref collection with [ForeignKey] Configure the correct end as principal for self-ref collection with [ForeignKey] Oct 18, 2021
@AndriySvyryd AndriySvyryd merged commit 896f4e1 into release/6.0 Oct 18, 2021
@AndriySvyryd AndriySvyryd deleted the Issue26364 branch October 18, 2021 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants