← Back to branch summary

~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to docs/locks.rst

  • Committer: Stewart Smith
  • Date: 2010-11-07 04:22:31 UTC
  • mto: (1911.1.2 build)
  • mto: This revision was merged to the branch mainline in revision 1912.
  • Revision ID: stewart@flamingspork.com-20101107042231-ola4sl7j0qvg58tz
https://launchpad.net/bugs/668880
fix ARCHIVE storage engine calling exit (lintian warning). Was because we were linking in libinternal into libazio, which links into archive plugin. Just link libinternal into the command line utilities.

Show diffs side-by-side

added added

removed removed

Lines of Context:
docs/locks.rst
1
 
User Defined Locks
2
 
===================
3
 
 
4
 
A user can create a "lock" which is scoped to their user space. Multiple
5
 
session of the user can see the lock.
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
 
.. todo::
24
 
 
25
 
   deleted or released? are locks recursive?
26
 
 
27
 
Please note, get_lock() was designed to be compatible with MySQL. If you
28
 
hold any locks when calling get_lock() they will be released. For this
29
 
reason you may want to consider calling get_locks() instead.
30
 
 
31
 
Information on all barriers can be found in the DATA_DICTIONARY.USER_LOCKS
32
 
table;