A database normally puts a row/field/table level lock to prevent other users from changing the same data until the first user has finished.
field/row level locking should be used rather than table level because table level locking will lock out others users unnecessarily.
Obviously you will have to implement an algorythm to detect the locks so that other users can detect the locks, wait and go back for the data.
From: <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: "cocoon" <[EMAIL PROTECTED]> Subject: database transaction handling Date: Sat, 26 Jul 2003 01:54:18 +0200
Hello, i'm still a newbie ;-) How to realize the database transaction handling? What do you suggest? What kind of C2 components should I use? Example: Editing data in a DB via WWW. How to exclude the possibilty of editing the same row by two different users at the same time. Thankful for help
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
