← 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-26 22:40:33 UTC
  • mto: This revision was merged to the branch mainline in revision 1958.
  • Revision ID: brian@tangent.org-20101126224033-yt9a3o82w2rhaihp
Adding select for update test with flush locks engaged.

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
If a session should exit, whatever locks it was holdering will be deleted.
 
22
 
 
23
Please note, get_lock() was designed to be compatible with MySQL, if you
28
24
hold any locks when calling get_lock() they will be released. For this
29
25
reason you may want to consider calling get_locks() instead.
30
26