← Back to branch summary

~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to docs/locks.rst

  • Committer: Padraig O'Sullivan
  • Date: 2010-12-03 19:16:09 UTC
  • mto: (1975.1.2 build)
  • mto: This revision was merged to the branch mainline in revision 1976.
  • Revision ID: osullivan.padraig@gmail.com-20101203191609-7s81iwt33vrgmz9v
Some re-factoring based on feedback from Monty on IRC.

Show diffs side-by-side

added added

removed removed

Lines of Context:
docs/locks.rst
1
 
User Defined Locks
 
1
User Definied Locks
2
2
===================
3
3
 
4
4
A user can create a "lock" which is scoped to their user space. Multiple
18
18
 
19
19
SELECT is_used_lock();
20
20
 
21
 
If a session should exit, whatever locks it was holding will be deleted.
22
 
 
23
 
.. todo::
24
 
 
25
 
   deleted or released? are locks recursive?
26
 
 
27
 
Please note, get_lock() was designed to be compatible with MySQL. If you
 
21
SELECT wait_for_lock();
 
22
 
 
23
SELECT release_lock_and_wait();
 
24
 
 
25
If a session should exit, whatever locks it was holdering will be deleted.
 
26
 
 
27
Please note, get_lock() was designed to be compatible with MySQL, if you
28
28
hold any locks when calling get_lock() they will be released. For this
29
29
reason you may want to consider calling get_locks() instead.
30
30
 
 
31
release_lock_and_wait() released the named lock, and then waits for another
 
32
session to try to obtain ownership. If it does not own the lock, it returns
 
33
with a zero.
 
34
 
31
35
Information on all barriers can be found in the DATA_DICTIONARY.USER_LOCKS
32
36
table;