← Back to branch summary

~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to docs/locks.rst

  • Committer: Mark Atwood
  • Date: 2011-08-11 03:05:03 UTC
  • mfrom: (2385.1.12 refactor4)
  • Revision ID: me@mark.atwood.name-20110811030503-rp9xjihc5x3y0x4q
merge lp:~olafvdspek/drizzle/refactor4

Show diffs side-by-side

added added

removed removed

Lines of Context:
docs/locks.rst
4
4
A user can create a "lock" which is scoped to their user space. Multiple
5
5
session of the user can see the lock.
6
6
 
7
 
SELECT GET_LOCK();
8
 
 
9
 
SELECT GET_LOCKS();
10
 
 
11
 
SELECT RELEASE_LOCK();
12
 
 
13
 
SELECT RELEASE_LOCK();
14
 
 
15
 
SELECT RELEASE_LOCKS();
16
 
 
17
 
SELECT is_free_lock();
18
 
 
19
 
SELECT is_used_lock();
20
 
 
21
 
If a session should exit, whatever locks it was holding will be deleted.
22
 
 
23
 
FIXME: deleted or released? are locks recursive?
 
7
.. code-block:: mysql
 
8
   
 
9
   SELECT GET_LOCK();
 
10
 
 
11
   SELECT GET_LOCKS();
 
12
 
 
13
   SELECT RELEASE_LOCK();
 
14
 
 
15
   SELECT RELEASE_LOCK();
 
16
 
 
17
   SELECT RELEASE_LOCKS();
 
18
 
 
19
   SELECT is_free_lock();
 
20
 
 
21
   SELECT is_used_lock();
 
22
 
 
23
If a session should exit, whatever locks it was holding will be released.
 
24
 
 
25
.. todo::
 
26
 
 
27
        are locks recursive?
24
28
 
25
29
Please note, get_lock() was designed to be compatible with MySQL. If you
26
30
hold any locks when calling get_lock() they will be released. For this