-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
In-Memory concurrency check is not doing a sequence check when using a byte array type #12214
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
customer-reported
regression
type-bug
Milestone
Comments
ajcvickers
added a commit
that referenced
this issue
Jun 21, 2018
Fixes #12214 Fix is to use structural equality all the time for concurrency checks. This matches more closely the way the check works on real database systems.
ajcvickers
added
Servicing-consider
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
patch-approved
and removed
Servicing-consider
labels
Jun 21, 2018
@ajcvickers This issue is approved for patch and the release\2.1 branch is now open for merging. Please ensure:
|
ajcvickers
added a commit
that referenced
this issue
Jun 27, 2018
Fixes #12214 Fix is to use structural equality all the time for concurrency checks. This matches more closely the way the check works on real database systems.
ajcvickers
added a commit
that referenced
this issue
Jun 27, 2018
Fixes #12214 Fix is to use structural equality all the time for concurrency checks. This matches more closely the way the check works on real database systems.
ajcvickers
added a commit
that referenced
this issue
Jun 28, 2018
ajcvickers
added a commit
that referenced
this issue
Jun 28, 2018
ajcvickers
added a commit
that referenced
this issue
Jun 28, 2018
ajcvickers
added a commit
that referenced
this issue
Jun 28, 2018
This was referenced Jul 30, 2021
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
customer-reported
regression
type-bug
Describe what is not working as expected.
I am using a byte array for my concurrency check and when using automapper to go from my dto to my ef entity object it causes the following error when saving with the in-memory provider for my tests:
Exception thrown: 'Microsoft.EntityFrameworkCore.DbUpdateConcurrencyException' in ConcurrencyTest.dll
An unhandled exception of type 'Microsoft.EntityFrameworkCore.DbUpdateConcurrencyException' occurred in ConcurrencyTest.dll
Conflicts were detected for instance of entity type 'Customer' on the concurrency token properties {'RowVersion'}. Consider using 'DbContextOptionsBuilder.EnableSensitiveDataLogging' to see the conflicting values.
The error has started occurring when upgrading my project to 2.1. I narrowed it to #10158 where concurrency token checks were enabled for the in-memory provider. After reviewing the code I notice it is doing a equals check and possibly might require a equal sequence check if its a byte array?
Steps to reproduce
Further technical details
EF Core version: 2.1
Database Provider: Microsoft.EntityFrameworkCore.InMemory
Operating system: Windows 10
IDE: Visual Studio 2017 15.7.3
The text was updated successfully, but these errors were encountered: