Attaching entity and setting different IsModified values to different property prevent update #8265
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
Milestone
I am not quite sure if this is me doing something wrong, I am pretty sure I have been using this technique without any issues for a good while. But it might be possible that I might never have noticed that some fields were not updating. It might also be possible that the update only fail under very specific circonstances.
So far I have only reproduced the issue while having two property explicitly set to false and true on the second.
Also, it seems that by simply having another entity being saved within the same transaction automatically resolved problem, the IsModified was being taken into account properly.
Steps to reproduce
Further technical details
EF Core version: 1.1.1
Database Provider: (e.g. Microsoft.EntityFrameworkCore.SqlServer)
Operating system: Win10
IDE: (e.g. Visual Studio 2015)
Observed on EF Core 1.1.0 as well.
Similar issues
#7798
#7227
The text was updated successfully, but these errors were encountered: