Concurrency violation errors

  • Thread starter Thread starter John
  • Start date Start date
J

John

Hi

During db development one of the most frustrating thing is the Concurrency
Violation error which seems to be a general error message for any error
during saving of record(s). How can one debug such an error and get more
specific information on the underlying reason for error and the
fields/records responsible for it?

Thanks

Regards
 
John,

As you have done it well, then there should be seldom a concurrency error.
It is even mostly difficult to test (get them) because you should use two
operations seperately from each other to get those.

Therefore you should at least first tell how you created your checking on
concurrency. Because there are more ways to prevent concurrency problems
(not the errors because concurrency checking has to be done as it is at
least a little bit a business solution).

Any other answer you get now, will be a waste of time for the writter and
for you to look at it. Then you can better set your money on one of the
races in the UK.

However it is for sure not a general message. Normally as you have done it
well, you would see them very seldom as optimistic concurrency is based on
that.


Cor
 
How are you doing your updates? Are you using strongly typed datasets and
the auto-generated SQL statements that do the updates? Or are you rolling
your own?

RobinS.
 
Back
Top