You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When configuring multiple entities with table splitting and row version concurrency tokens, updating the dependents without the principal entity will throw an unexpected DbUpdateConcurrencyException.
If the principal entity (Foo) is tracked via ChangeTracker, then the updates persist properly. This occurs regardless of whether a transaction is used or not.
@Westboldyi can you please submit a minimal, runnable console program that shows the error happening? It's hard to piece together exactly what you're doing from a screenshot and partial snippets.
No, this is a bug. We need to either collapse both updates into one command (by indexing using key values instead of entries) or to separate the two commands in different batches.
When configuring multiple entities with table splitting and row version concurrency tokens, updating the dependents without the principal entity will throw an unexpected
DbUpdateConcurrencyException
.If the principal entity (
Foo
) is tracked via ChangeTracker, then the updates persist properly. This occurs regardless of whether a transaction is used or not.EF Configs:
Include provider and version information
EF Core version:
Database provider: Postgresql
Target framework: .NET 8
Operating system: WIN 10
IDE:VS 2022
The text was updated successfully, but these errors were encountered: