How to ignore a DbUpdateConcurrencyException when deleting an entity

Question

I have an app that reads a lot of data into memory and processes it in a batches.

What I want is for entity framework to ignore DbUpdateConcurrencyException when deleting an entity that has already been deleted.

The reason is that by the time an entity has been processed and marked for deletion, it may already have been deleted from the DB.

Obliviously deleting a row that has already been deleted isn't a problem and shouldn't cause an error, I just need a way to tell entity framework that :)

Example

Db.Entry(itemToRemove).State = EntityState.Deleted;
Db.SaveChanges();

Causes an error if itemToRemove has already been deleted.

Note: Db.Configuration.ValidateOnSaveEnabled = false; doesn't fix this as another thread suggested.

Answer 1

How about?

Db.Entry(itemToRemove).State = EntityState.Deleted;

bool saveFailed;
do
{
    saveFailed = false;
    try
    {
       Db.SaveChanges();
    }
    catch(DbUpdateConcurrencyException ex)
    {
       saveFailed = true;
       var entry = ex.Entries.Single();
       //The MSDN examples use Single so I think there will be only one
       //but if you prefer - do it for all entries
       //foreach(var entry in ex.Entries)
       //{
       if(entry.State == EntityState.Deleted)
          //When EF deletes an item its state is set to Detached
          //http://msdn.microsoft.com/en-us/data/jj592676.aspx
          entry.State = EntityState.Detached;
       else
          entry.OriginalValues.SetValues(entry.GetDatabaseValues());
          //throw; //You may prefer not to resolve when updating
       //}
    }
} while (saveFailed);

More here: Resolving optimistic concurrency exceptions