~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to docs/locks.rst

  • Committer: Lee Bieber
  • Date: 2011-01-12 02:31:03 UTC
  • mfrom: (2068.7.5 session-fix)
  • mto: This revision was merged to the branch mainline in revision 2076.
  • Revision ID: kalebral@gmail.com-20110112023103-nmz26cv1j32jc6n3
Merge Brian - fix bug 527084 - DROP TABLE: getTableDefiniton returns EEXIST but doDropTable returns ENOENT leads to SIGSEGV

Show diffs side-by-side

added added

removed removed

Lines of Context:
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
 
 
25
23
Please note, get_lock() was designed to be compatible with MySQL. If you
26
24
hold any locks when calling get_lock() they will be released. For this
27
25
reason you may want to consider calling get_locks() instead.
28
26
 
29
27
Information on all barriers can be found in the DATA_DICTIONARY.USER_LOCKS
30
 
table;
 
28
table;
 
 
b'\\ No newline at end of file'