Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.4(EOL), 10.5, 10.6, 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL)
-
None
Description
GET_LOCK function does not work as expected in a stored program when character_set_database is set to ucs2.
--connection 1
|
delimiter |
|
CREATE PROCEDURE p1()
|
BEGIN
|
SELECT GET_LOCK('m1', 10000);
|
SELECT 'Query OK';
|
END;
|
|
|
delimiter ;
|
|
SET character_set_database=ucs2;
|
SET CHARACTER SET DEFAULT;
|
|
--connection 2
|
SET character_set_database=ucs2;
|
SET CHARACTER SET DEFAULT;
|
SELECT GET_LOCK('m1', 0);
|
|
--connection 1
|
CALL p1();
|
When the procedure is called from session-1, procedure `p1` must wait for resource `m1` to be released from session-2.