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
Issue #10613 introduced null-checking on required properties when using the In-Memory provider.
After updating however all my unit tests with record creation are now failing because I haven't set the RowVersion (ConcurrencyToken) property when creating an entity in my service.
As far as I can see this is incorrect behaviour as the ConcurrencyToken value is/should always (be) generated by the database engine.
Could properties that are defined as IsConcurrencyToken and ValueGeneratedOnAddOrUpdate either be ignored by the check or have a value generated for them so the check doesn't fail?
Is there a way to hook into the In-Memory provider to handle the generation of the ConcurrencyToken property values?
File a bug
Issue #10613 introduced null-checking on required properties when using the In-Memory provider.
After updating however all my unit tests with record creation are now failing because I haven't set the
RowVersion
(ConcurrencyToken) property when creating an entity in my service.As far as I can see this is incorrect behaviour as the ConcurrencyToken value is/should always (be) generated by the database engine.
Could properties that are defined as
IsConcurrencyToken
andValueGeneratedOnAddOrUpdate
either be ignored by the check or have a value generated for them so the check doesn't fail?Is there a way to hook into the In-Memory provider to handle the generation of the
ConcurrencyToken
property values?Include your code
Include stack traces
Include provider and version information
EF Core version: 6.0.0
Database provider: Microsoft.EntityFrameworkCore.InMemory
Target framework: .NET 6.0
Operating system: Windows 10
IDE: Visual Studio 2020 17.0.1
The text was updated successfully, but these errors were encountered: