summaryrefslogtreecommitdiff
path: root/sql/sql_delete.cc
diff options
context:
space:
mode:
authorKonstantin Osipov <kostja@sun.com>2009-12-01 16:51:50 +0300
committerKonstantin Osipov <kostja@sun.com>2009-12-01 16:51:50 +0300
commit386b95dfef19d0ca248a72783e14dda5a925ec17 (patch)
tree638c795bd178a4fb46d2eecae55390c861d0a266 /sql/sql_delete.cc
parentf198e8bee9abad277607a427842edfae60ea35f1 (diff)
downloadmariadb-git-386b95dfef19d0ca248a72783e14dda5a925ec17.tar.gz
Backport of:
------------------------------------------------------------ revno: 2630.8.3 committer: Dmitry Lenev <dlenev@mysql.com> branch nick: mysql-6.0-3726-w4 timestamp: Thu 2008-06-05 10:48:36 +0400 message: WL#3726 "DDL locking for all metadata objects". After-review fixes in progress. Adjust some comments that were using old terminology (name locks instead of exclusive metadata locks), brought some of them up-to-date with current situation in code.
Diffstat (limited to 'sql/sql_delete.cc')
-rw-r--r--sql/sql_delete.cc3
1 files changed, 2 insertions, 1 deletions
diff --git a/sql/sql_delete.cc b/sql/sql_delete.cc
index f5c6dfd8986..612f9d1954d 100644
--- a/sql/sql_delete.cc
+++ b/sql/sql_delete.cc
@@ -1079,7 +1079,8 @@ static bool mysql_truncate_by_delete(THD *thd, TABLE_LIST *table_list)
normally can't safely do this.
- We don't want an ok to be sent to the end user.
- We don't want to log the truncate command
- - If we want to have a name lock on the table on exit without errors.
+ - If we want to keep exclusive metadata lock on the table (obtained by
+ caller) on exit without errors.
*/
bool mysql_truncate(THD *thd, TABLE_LIST *table_list, bool dont_send_ok)