-
-
Notifications
You must be signed in to change notification settings - Fork 580
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
Concurrency check is missing in Updates #469
Comments
Will consider it. |
My suggestion would be that the operation should throw a concurrency exception. |
Support added with latest version 3.4.7+. EFCore.BulkExtensions/EFCore.BulkExtensions.Tests/EFCoreBulkTestAtypical.cs Lines 57 to 103 in f867620
|
@borisdj I can't seem to get this to work (I'm using upsert), TimeStampInfo seems to always be null. I've defined the RowVersion as RowVersion type in the table? Does the library support optimistic locking via ConcurrencyCheck attribute as well? |
Tried both, always receive TimeStampInfo to be null:
|
@defunky in case it is still valid - adding SetOutputIdentity = true fixes the issue |
This is a duplicate of #209, which has been unfortunately closed.
Entity Framework generates a WHERE close on updates to check concurrent updates for each entity that has a concurrency token (timestamp). The bulk updates don't generate those WHERE clauses and skip EF concurrency checks.
Any plan to add support for concurrency checks?
The text was updated successfully, but these errors were encountered: