Closed chris-stormideas closed 1 year ago
@chris-stormideas - Please share a full repro code which demonstrate the issue. Your code snippets contains too many missing parts for us to effectively reproduce.
EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.
I have raised another issue, however it was incorrectly closed.
The following mapping worked fine in 2.2, no longer works with 3.0. The Cast (of type
MovieCastMember
) mapping throws. The OwnsMany before works fine, and other OwnsMany throw/work.The
MovieCastMember
is not mapped anywhere else. The previous issue was closed due to: https://github.com/aspnet/EntityFrameworkCore/issues/18167#issuecomment-537115340 But it should be clear in the code, this is not the case. There is also a type calledCastMember
which is not the type that is having the issue.The
MovieCastMember
type is a relational object that associates aMovie
with aCastMember
The
ConfigureRoot
looks like this:Stack Trace
Further technical details
EF Core version: 3.0 Database provider: Microsoft.EntityFrameworkCore.SqlServer/InMemory Target framework: .NET Core 3.0 Operating system: Manjaro 18.0.4 IDE: Rider 2019.2.2