Hi,
John Comerford wrote:
Hi Folks,
My problem is that the IS_FREE_LOCK always returns true.
I have done some testing with two instances of the Query Browser
running. In one I execute:
SELECT GET_LOCK('testing',10)
> 1
In the second I execute :
SELECT IS_FREE_LOCK('testing');
> 1
Maybe I have misinterpreted the scope of the lock functions, my
understanding was that the GET_LOCK should create a lock and the lock
should remain until a RELEASE_LOCK command is issued or the process that
created it terminates, is this correct ? If this is true anybody got
any ideas why the IS_FREE_LOCK is always true ?
I am trying with the mysql command-line client and having no trouble:
mysql> SELECT GET_LOCK('testing',10) ;
+------------------------+
| GET_LOCK('testing',10) |
+------------------------+
| 1 |
+------------------------+
1 row in set (0.00 sec)
In another terminal,
mysql> SELECT IS_FREE_LOCK('testing');
+-------------------------+
| IS_FREE_LOCK('testing') |
+-------------------------+
| 0 |
+-------------------------+
1 row in set (0.00 sec)
Looks fine. So I suspect what's really happening is Query Browser is
closing its connection, or something like that.
Baron
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
