Concurrency via SqlCommand.ExecuteNonQuery

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When using a SqlDataAdapter generated Update StoredProc,
the DataAdapter.UpdateCommend (correctly) returns a
DBConcurrency error.

Using the same stored proc, instead of using the
dataAdapter, I create a SqlCommand object and add all of
the required parameters filled with the appropriate
values of the current and original values. I then use
ExecuteNonQuery to do the update. I get no exception of
any kind when there is a concurrency problem.

Is there no way to handle concurrency issues without
using the DataAdapter?
 
1) Use an appropriate WHERE clause to insure that no records are updated if
there is a conflict, and an output parameter that returns the number of
records affected.

2) If records effected is zero, throw a DBConcurrencyException.

--Bob
 
Thanks Bob
That was helpful.
-----Original Message-----
1) Use an appropriate WHERE clause to insure that no records are updated if
there is a conflict, and an output parameter that returns the number of
records affected.

2) If records effected is zero, throw a DBConcurrencyException.

--Bob




.
Click to expand...
 
Back
Top