summaryrefslogtreecommitdiff
path: root/innobase
diff options
context:
space:
mode:
authorunknown <heikki@hundin.mysql.fi>2004-12-27 17:28:17 +0200
committerunknown <heikki@hundin.mysql.fi>2004-12-27 17:28:17 +0200
commit030842edaadf34fe0547bde9d46c6bf285416c88 (patch)
treeee47ebce551295fb2cbab1373d8ab30722927adf /innobase
parent5f6d8e65262227a8e6431a57fe832fd335c6b2e4 (diff)
downloadmariadb-git-030842edaadf34fe0547bde9d46c6bf285416c88.tar.gz
row0mysql.c:
Merge the two FOREIGN KEY bug fixes from 4.0, and add a TODO comment innobase/row/row0mysql.c: Merge the two FOREIGN KEY bug fixes from 4.0, and add a TODO comment
Diffstat (limited to 'innobase')
-rw-r--r--innobase/row/row0mysql.c6
1 files changed, 6 insertions, 0 deletions
diff --git a/innobase/row/row0mysql.c b/innobase/row/row0mysql.c
index 47f1f4c444c..e2b89cba866 100644
--- a/innobase/row/row0mysql.c
+++ b/innobase/row/row0mysql.c
@@ -2598,6 +2598,12 @@ row_drop_table_for_mysql(
goto funct_exit;
}
+ /* TODO: could we replace the counter n_foreign_key_checks_running
+ with lock checks on the table? Acquire here an exclusive lock on the
+ table, and rewrite lock0lock.c and the lock wait in srv0srv.c so that
+ they can cope with the table having been dropped here? Foreign key
+ checks take an IS or IX lock on the table. */
+
if (table->n_foreign_key_checks_running > 0) {
ut_print_timestamp(stderr);