title: How to ignore a DbUpdateConcurrencyException when deleting an entity
body: <p>I have an app that reads a lot of data into memory and processes it in a batches. </p>
  
  <p>What I want is for entity framework to ignore <code>DbUpdateConcurrencyException</code> when deleting an entity that has already been deleted. </p>
  
  <p>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.</p>
  
  <p>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 :) </p>
  
  <p>Example</p>
  
  <pre><code>Db.Entry(itemToRemove).State = EntityState.Deleted;
  Db.SaveChanges();
  </code></pre>
  
  <p>Causes an error if <code>itemToRemove</code> has already been deleted.</p>
  
  <p>Note: <code>Db.Configuration.ValidateOnSaveEnabled = false;</code> doesn't fix this as another thread suggested.</p>