how to avoid concurrency while dealing with dataset
-
What happens when u try to update data in a dataset in .NET while the record is already deleted in SQL SERVER as backend? OR What is concurrency? How will you avoid concurrency when dealing with dataset? (One user deleted one row after that another user through his dataset was trying to update same row. What will happen? How will you avoid the problem?)
-
What happens when u try to update data in a dataset in .NET while the record is already deleted in SQL SERVER as backend? OR What is concurrency? How will you avoid concurrency when dealing with dataset? (One user deleted one row after that another user through his dataset was trying to update same row. What will happen? How will you avoid the problem?)
I would implement record locking so that one user at a time had the right to edit a piece of data.
Christian Graus Driven to the arms of OSX by Vista.
-
What happens when u try to update data in a dataset in .NET while the record is already deleted in SQL SERVER as backend? OR What is concurrency? How will you avoid concurrency when dealing with dataset? (One user deleted one row after that another user through his dataset was trying to update same row. What will happen? How will you avoid the problem?)
Sounds a lot like a homework question...
-
Sounds a lot like a homework question...
we need answers not assements
-
we need answers not assements
Nice. Way to reply to a two year old message...