Arthur Vickers
Arthur Vickers
The overload avoided a breaking change when design-time support was added.
@voroninp You can't use constructor injection, but you can use `DbContext` as a service locator, and it will look in the application service provider if the service is not found...
My only concern here is whether this could cause issues with existing code that assumes `DbUpdateConcurrencyException` _must mean_ actual rows affected is different from expected rows affected, since there has...
@roji EF should be wrapping the provider-specific error in a `DbUpdateException`. `DbUpdateConcurrencyException` derives from `DbUpdateException`, so if code is currently catching only `DbUpdateException`, then it should still work the same...
@roji I went and looked at the original issue. It seems that Npgsql is wrapping the `DbUpdateException` in an `InvalidOperationException`, which is strange for an error that comes from `SaveChanges`....
Note from triage: consider using System.CommandLine; see #6850 and #30487.
This issue is lacking enough information for us to be able to fully understand what is happening. Please attach a small, runnable project or post a small, runnable code listing...
Note for EF team: the problem here is that the JSON document is used `Id` as its primary key, but EF is not picking up on this, so the resulting...
Closing this since #29380 is tracking the root cause.
I am not able to reproduce this--see my code below. Please attach a small, runnable project or post a small, runnable code listing that reproduces what you are seeing so...