ADO.NET DBConcurrencyException - Trying to update an already deleted row

Question

Why is ADO.NET throwng a DBConccurencyException, when I try to update a row that is already deleted by another process, instead of just ignoring the deleted row?

Is there any available option in ADO.NET to ignore this fact?

I am using SQLCommandBuilder with ConflictOption set to ConflictOption.OverwriteChanges.

This is by design. Why not just handle the exception and carry on gracefully? — Darbio, May 12 '11 at 12:26
http://msdn.microsoft.com/en-us/magazine/cc163924.aspx take a look at the code in Figure 3... — Darbio, May 12 '11 at 12:33

score 1 · Answer 1 · edited May 12 '11 at 12:33

1

You can use the DataViewRowState enumeration to select only the modified rows.

var rowsToUpdate =
            dataTable.Select(null, null, DataViewRowState.ModifiedOriginal);

edited May 12 '11 at 12:33

Greg B

14,597
18
87
141

answered May 12 '11 at 12:32

Dutch Nico

250
2
8

how does this work? Is ADO.NET querying the row immediately before updating it? – Rookian May 12 '11 at 14:25
ado.net checks the state before updating. If the row has been deleted it can't access it any longer – Dutch Nico May 12 '11 at 15:50

ADO.NET DBConcurrencyException - Trying to update an already deleted row

1 Answers1