ot;gerald_clark" <[EMAIL PROTECTED]>
To: "Richard Clarke" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, June 01, 2004 8:39 PM
Subject: Re: GET_LOCK(str,timeout) behaviour
> GET_LOCK is just a string lock, and has nothing to do with tables.
> Use L
GET_LOCK is just a string lock, and has nothing to do with tables.
Use LOCK TABLES instead.
Richard Clarke wrote:
The manual indicates that a GET_LOCK expires automatically when a new
GET_LOCK is issued. Can someone explain to me how this behaviour could
possibly be the most useful?
I wish to use
On Tue, Dec 31, 2002 at 01:49:00PM -0500, 'Bob Diss' wrote:
> Re: GET_LOCK locks
>
> Is there a way to show the status of locks created in this fash-
> ion? I'm looking for something that would list the locks
> current in existance, and which thread is holding it
Re: GET_LOCK locks
Is there a way to show the status of locks created in this fash-
ion? I'm looking for something that would list the locks
current in existance, and which thread is holding it.
filter: sql, mysql, mysql
It is just a string.
It does not lock anything in the database.
It sets a semaphore to be tested by other programs.
You need to make sure ALL programs updating your database use
the string locks, and that the stringlock will be unique for every
record.
you could youse something like database-table
It's purely advisory locking. You aren't locking anything other
than a certain value within the server itself. The benefit comes
only if all clients agree to use the same advisory locking schema.
-Tilghman
--
"There cannot be a crisis today. My schedule is already full."
--Henry Kissing
