From ffc7ab8c35c22459394ed3c923da4a45c4e71746 Mon Sep 17 00:00:00 2001 From: John Harris Date: Wed, 13 Feb 2019 19:58:13 +0530 Subject: [PATCH] Updated ReadMe.md --- ReadMe.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ReadMe.md b/ReadMe.md index f26f810..2dab6df 100644 --- a/ReadMe.md +++ b/ReadMe.md @@ -150,9 +150,9 @@ When a data is read from the DB and when business logic is applied to the data, The state of the values in each of the transaction produces a conflict when the system attempts to save the changes and identifies using the concurrency token that the values being updated to the database are not the Original values that was read from the database and it throws DbUpdateConcurrencyException. -[Reference: docs.microsoft.com](https://docs.microsoft.com/en-us/visualstudio/data-tools/handle-a-concurrency-exception?view=vs-2017) +[Reference: docs.microsoft.com](https://docs.microsoft.com/en-us/ef/core/saving/concurrency) -The general approach to handle the concurrency conflict is [Reference MSDN]: +The general approach to handle the concurrency conflict is: 1. Catch **DbUpdateConcurrencyException** during SaveChanges 2. Use **DbUpdateConcurrencyException.Entries** to prepare a new set of changes for the affected entities.