MySQL will do what you want. It's a black box to store an manupulate
data. Most of the time the transactions are so fast, it doesn't
matter. In the case of mySQL, it's multi user by design and if one
is really worried about it, there's COMMIT and ROLLBACK.
SQL Lite is not multi-user.
Hi all,
this is a bit off topic, but maybe someone can give me some helpful hints.
Is someone of you working with databases with multiple users?
If yes, how do you handle "concurrent transactions"?
I mean how do you solve the possible overwriting of data when both
users work with
cursors and are allowed to update data and how do you update a
cursor (on the fly?)
when its data may have been updated?
Know what I mean?
I searched the net and found some hints, but maybe you have some really clever
solutions that you are willing to share :-)
Thanks in advance!
Best
Klaus Major
[EMAIL PROTECTED]
http://www.major-k.de
--
stephen barncard
s a n f r a n c i s c o
- - - - - - - - - - - -
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
