Is there any way I can tell EF to not worry about the number of rows a DELETE
or UPDATE
do or don\'t do?
I\'m trying to delete
I think the behavior of EF is correct - simply you must execute commands only for objects which are present in DB. It is not for scenarios like: "I will try it and we will see...". If you can't be sure that object exists in DB and you don't want to do round trip (which I think is the best idea because deleting detached object can have several other pitfalls especially if object participates in independent associations) you should use DbContext.Database.SqlCommand
and run store procedure.
The correct way to handle DbUpdateConcurrencyException
is described here => After each exception you should resolve confilicts (in your case it means remove problematic entity from DbContext) and execute SaveChanges
again.