-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
InverseProperty attribute doesn't always resolve navigation property ambiguity #7266
Comments
Only this fixed the issue modelBuilder.Entity<CarResponse>(entity =>
{
entity.HasOne<CarRequest>()
.WithOne(r => r.AcceptedCarResponse)
.HasForeignKey<CarResponse>("AcceptedResponseId");
}); |
@AndriySvyryd looks like this could be a regression from previous behavior based on the title. |
…th InversePropertyAttribute. Fixes #7266
This is a new regression in 1.1.1 |
@AndriySvyryd just to be sure, is it a regression we introduced in 1.1.1 that we should fix before we ship or a regression in 1.1 that we should fix in 1.1.1? Thanks! |
@divega It was introduced in 1.1.1 |
This patch bug is approved. Please use the normal code review process w/ a PR and make sure the fix is in the correct branch, then close the bug and mark it as done. |
InvalidOperationException: Unable to determine the relationship represented by navigation property 'CarRequest.AcceptedCarResponse' of type 'CarResponse'. Either manually configure the relationship, or ignore this property from the model.
Stack trace:
Steps to reproduce
@rowanmiller has a project.
I can drop updated files into Skype for Business
Further technical details
EF Core version: 1.2.0-preview1-22936
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows 10 14986 x64 En-US
IDE: Visual Studio 2015 Enterprise Update 3 En-US
The text was updated successfully, but these errors were encountered: