← Back to branch summary

~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to docs/locks.rst

  • Committer: Lee Bieber
  • Date: 2011-01-15 04:24:34 UTC
  • mfrom: (2086.1.3 build)
  • Revision ID: kalebral@gmail.com-20110115042434-f4g9hd4vu3rw6bfx
Merge Stewart - some documentation clean up
Merge Patrick - fix bug 693130: Tests depending on archive engine should be skipped if archive isn't enabled
Merge Patrick - fix bug 697292: The have_valgrind include file in the test has the opposite effect

Show diffs side-by-side

added added

removed removed

Lines of Context:
docs/locks.rst
20
20
 
21
21
If a session should exit, whatever locks it was holding will be deleted.
22
22
 
 
23
FIXME: deleted or released? are locks recursive?
 
24
 
23
25
Please note, get_lock() was designed to be compatible with MySQL. If you
24
26
hold any locks when calling get_lock() they will be released. For this
25
27
reason you may want to consider calling get_locks() instead.
26
28
 
27
29
Information on all barriers can be found in the DATA_DICTIONARY.USER_LOCKS
28
 
table;
 
 
b'\\ No newline at end of file'
 
30
table;