Store update, insert, or delete statement affected an unexpected number of rows (0) EntityFramework [duplicate]

Answer 1

Add this to your edit.cshtml

@Html.HiddenFor(model => model.Id)

I had this issue and found that the ID was coming across as 0 since it was not on the page.

I also have this on my ViewModel (I am using the view model approach)

[HiddenInput(DisplayValue = false)]
[Key]
public int Id { get; set; }

Answer 2

add the following overload to my DbContext class:

using System.Data.Entity.Core.Objects;
using System.Data.Entity.Infrastructure;

public class MyDbContext: DbContext {
...
        public int SaveChanges(bool refreshOnConcurrencyException, RefreshMode refreshMode = RefreshMode.ClientWins) {
            try {
                return SaveChanges();
            }
            catch (DbUpdateConcurrencyException ex) {
                foreach (DbEntityEntry entry in ex.Entries) {
                    if (refreshMode == RefreshMode.ClientWins)
                        entry.OriginalValues.SetValues(entry.GetDatabaseValues());
                    else
                        entry.Reload();
                }
                return SaveChanges();
            }
        }
}

Then called SaveChanges(true) wherever applicable.

Answer 3

I ran into this error message as well. What caused my error was primary / foreign key conflicts. I had pushed some new data into my DB and my foreign key values were off (mistake in my upload script).

Use SQL Profiler to help track down the offending insert script, this will likely help you discover what the issue with the update.

Hope this helps anyone else with similar issues.

Answer 4

There is a conflict, as you are using optimistic locking. Resolve concurrency issues using the ObjectStateManager entries, and Save changes again. Some sample code is there in MSDN site.

Answer 5

In my case, I had a composite key and was trying to update part of it (3 columns constitutes a composite key, out of which i was updating 3rd column only) but EF didn't allow changing key values for the same object, I achieved updating the record through:

Context.Database.ExecuteSqlCommand(udpateCommand);

Answer 6

If ever you came across to this problem and non of the above solutions helped you, maybe you can try this. I also had this weird issue, and the way I was able to have it fixed is I have set the a field to primary key and have it auto increment or set to Identity. Say you have the Person table and you have a personID maybe, set it to primary key and make sure it is auto incremented.