s??
Randy
-Original Message-
From: Cal Evans [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 24, 2001 4:10 PM
To: Randy Johnson; [EMAIL PROTECTED]
Subject: RE: Doing multiple updates
Randy,
My recommendation (and there are probably many people who will disagree with
me) is to use a "so
al Message-
From: Cal Evans [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 24, 2001 4:10 PM
To: Randy Johnson; [EMAIL PROTECTED]
Subject: RE: Doing multiple updates
Randy,
My recommendation (and there are probably many people who will disagree with
me) is to use a "soft-lock" sche
Can somebody provide me with some sample code for the following. I read it
over in the manual but am still lost.
thanks
Randy
+++
Sounds like you want a mutex and you can use get_lock and release_lock in
mysql for that.
http://www.mysql.com/doc/M/i/Miscellaneous_functions.html
GET_LO
use a soft lock
like you've described. I dunno.
-Original Message-
From: Cal Evans [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 24, 2001 9:10 PM
To: Randy Johnson; [EMAIL PROTECTED]
Subject: RE: Doing multiple updates
Randy,
My recommendation (and there are probably many
Randy,
My recommendation (and there are probably many people who will disagree with
me) is to use a "soft-lock" schema.
In your account table, add a field named lockedBy. I usually add a field
named lockedAt also as a timestamp.
the basic flow is this:
1: Check to see if the record has somethi
Sounds like you want a mutex and you can use get_lock and release_lock in
mysql for that.
http://www.mysql.com/doc/M/i/Miscellaneous_functions.html
GET_LOCK(str,timeout)
Tries to obtain a lock with a name given by the string str, with a timeout
of timeout seconds. Returns 1 if the lock was obta