|
-
Nov 3rd, 2002, 07:19 AM
#1
Concurrency anyone?
Hi Folks,
How do you manage concurrency issues in your application? Do you have some method of propogating the concurrency issues back to the client or do you usually let the database take care of the problem?
Either way I am interested to know more on the subject. In our application we have completely avoided dealing with concurrency issues. As a result of that the only option that remains with the client is to update the database with the latest change made by the user.
This is not a really practical solution everywhere, but that is the one that works for most people. I have so far seen only one application where the "underlying value" property was actually used.
Another doubt that I have is how do you actually manage concurrency if all you are planning to use are "INSERT STATEMENTS" in your code?
How do you manage concurrency through a stored procedure?
Cheers!
Abhijit
Everything that has a computer in will fail. Everything in your life, from a watch to a car to, you know, a radio, to an iPhone, it will fail if it has a computer in it. They should kill the people who made those things.- 'Woz'
save a blobFileStreamDataTable To Text Filemy blog
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|