Arthur Vickers
Arthur Vickers
@pgrm We haven't root-caused the issue yet. It's certainly only an issue in specific cases. If you're concerned about perf here, then I think you'll need to do perf testing...
This issue is in the Backlog milestone. This means that it is not planned for the next release (EF Core 8.0). We will [re-assess the backlog](https://docs.microsoft.com/ef/core/what-is-new/release-planning) following the this release...
> I get an exception that says the column name EmployeeId is not valid. I am not able to reproduce this. Please attach a small, runnable project or post a...
@ComptonAlvaro Yes. I used your code, but did not see any exceptions thrown.
@ComptonAlvaro I didn't run your code directly because I saw it had a U.I. I ripped out the model and query and ran it in a console app. I may...
Console is always best.
@ComptonAlvaro This code attempts to use the same foreign key for two different relationships: ```C# paramEmployeefiguracion .HasMany(x => x.Telephones) .WithOne() .HasForeignKey("IDEmployee"); paramEmployeefiguracion .HasMany(x => x.Emails) .WithOne() .HasForeignKey("IDEmployee"); ``` EF Core...
@danmoseley Who do we reach out these days for regressions in the DI libraries?
@lewing Yes this needs to escalate. Per policy, runtime needs to revert unless the fix can be made quickly. @danmoseley You asked me to ping you.
@ericstj Happy to disable a test once a release-blocking issue exists.