← 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-12-16 20:27:14 UTC
  • mto: (2002.1.4 clean) (2015.1.1 clean)
  • mto: This revision was merged to the branch mainline in revision 2003.
  • Revision ID: brian@tangent.org-20101216202714-fmzbmyoetoi8pr6j
First pass through, removing the need for us track the position in this
manner.

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
22
22
 
23
23
SELECT release_lock_and_wait();
24
24
 
25
 
If a session should exit, whatever locks it was holdering will be deleted.
 
25
If a session should exit, whatever locks it was holding will be deleted.
26
26
 
27
 
Please note, get_lock() was designed to be compatible with MySQL, if you
 
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