← Back to branch summary

~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to docs/locks.rst

  • Committer: Marisa Plumb
  • Date: 2010-12-07 21:20:16 UTC
  • mto: This revision was merged to the branch mainline in revision 1984.
  • Revision ID: marisa.plumb@gmail.com-20101207212016-20vkqo68uk0gtx0y
more sql doc modifications

Show diffs side-by-side

added added

removed removed

Lines of Context:
docs/locks.rst
1
 
User Definied Locks
 
1
User Defined 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 holdering will be deleted.
 
21
If a session should exit, whatever locks it was holding will be deleted.
22
22
 
23
 
Please note, get_lock() was designed to be compatible with MySQL, if you
 
23
Please note, get_lock() was designed to be compatible with MySQL. If you
24
24
hold any locks when calling get_lock() they will be released. For this
25
25
reason you may want to consider calling get_locks() instead.
26
26
 
27
27
Information on all barriers can be found in the DATA_DICTIONARY.USER_LOCKS
28
 
table;
 
28
table.
 
 
b'\\ No newline at end of file'