Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

The object cannot be deleted because it was not found in the ObjectStateManager in entity framework 5

Tags:

I'm trying to delete an object using EntityFramework 5 but i get this error. The object cannot be deleted because it was not found in the ObjectStateManager
I am using the Remove() method as DeleteObject() is not present in EF5. Can anyone help what am I missing?

This does not work for Remove

localDb.Customers.Remove(new Customer() { CustomerId = id });
                localDb.SaveChanges();

Another thing I tried from msdn to change the state to Deleted. But here it gives an error saying all the fields should be present. Is it necessary to get the complete record then delete?

var customer = new Customer(){ CustomerId = id };
                localDb.Customers.Attach(customer);

                localDb.Entry(customer).State = EntityState.Deleted;
                localDb.SaveChanges();

Any inputs?

like image 913
Rameez Ahmed Sayad Avatar asked Mar 26 '13 13:03

Rameez Ahmed Sayad


2 Answers

You can fetch the row from the database and then delete it, but this causes 2 round trips to the database.

If you want to do it in one hit, your second version with Attach will work - as long as the entity is not already loaded into the context.

The error you are getting is caused by EF validation which runs before any database write.

You can turn it off temporarily like this:

bool oldValidateOnSaveEnabled = localDb.Configuration.ValidateOnSaveEnabled;

try
{
  localDb.Configuration.ValidateOnSaveEnabled = false;

  var customer = new Customer { CustomerId = id };

  localDb.Customers.Attach(customer);
  localDb.Entry(customer).State = EntityState.Deleted;
  localDb.SaveChanges();
}
finally
{
  localDb.Configuration.ValidateOnSaveEnabled = oldValidateOnSaveEnabled;
}
like image 182
Nick Butler Avatar answered Sep 28 '22 06:09

Nick Butler


if you retrieved object from database then it's already attached to the context so you can delete by:

db.myTable.Remove(model);

but
if you just received model from edit or delete view by post or generated it yourself to avoid 2 trips to database then EF doesn't know about it and you get error with above line (..not found in the ObjectStateManager..) so you set its state to "Deleted" to inform EF by:

//generate it yourself if not posted from edit/delete view
//var model = new Model { Id = 123 };

//set to delete
db.Entry(model).State = EntityState.Deleted;
db.SaveChanges();
like image 26
Moji Avatar answered Sep 28 '22 06:09

Moji