← Back to branch summary

~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to docs/locks.rst

  • Committer: Brian Aker
  • Date: 2010-11-27 13:38:27 UTC
  • mfrom: (1955.1.3 quick)
  • Revision ID: brian@tangent.org-20101127133827-fowoi26sizq1zneg
Rollup of staging, mostly UDL

Show diffs side-by-side

added added

removed removed

Lines of Context:
docs/locks.rst
18
18
 
19
19
SELECT is_used_lock();
20
20
 
 
21
SELECT wait_for_lock();
 
22
 
 
23
SELECT release_lock_and_wait();
 
24
 
21
25
If a session should exit, whatever locks it was holdering will be deleted.
22
26
 
23
27
Please note, get_lock() was designed to be compatible with MySQL, if you
24
28
hold any locks when calling get_lock() they will be released. For this
25
29
reason you may want to consider calling get_locks() instead.
26
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
 
27
35
Information on all barriers can be found in the DATA_DICTIONARY.USER_LOCKS
28
36
table;