summaryrefslogtreecommitdiff
path: root/mysql-test/suite/innodb/t/innodb_bug60196-master.opt
diff options
context:
space:
mode:
authorunknown <kevin.lewis@oracle.com>2011-03-07 09:42:07 -0600
committerunknown <kevin.lewis@oracle.com>2011-03-07 09:42:07 -0600
commit08f128f63323924666caf4f7cb0d2b3c39d2b017 (patch)
treecc9c2374edd188996ec64dbc6bfab5ba15d2f032 /mysql-test/suite/innodb/t/innodb_bug60196-master.opt
parent85ea5564bd96c35ab55225285d4e80ee133d67d4 (diff)
downloadmariadb-git-08f128f63323924666caf4f7cb0d2b3c39d2b017.tar.gz
Bug#60196 / Bug#11831040
Setting lowercase_table_names to 2 on Windows causing Foreign Key problems This problem was exposed by the fix for Bug#55222. There was a codepath in dict0load.c, dict_load_foreigns() that made sure the table name matched case sensitive in order to load a referenced table into the dictionary as needed. If an engine is rebooted which accesses a table with foreign keys, and lower_case_table_names=2, then the table with foreign keys will get an error when it is changed (insert/updated/delete). Once the referenced tables are loaded into the dictionary cache by a select statement on those tables, the same change would succeed because the affected code path would not get followed.
Diffstat (limited to 'mysql-test/suite/innodb/t/innodb_bug60196-master.opt')
-rwxr-xr-xmysql-test/suite/innodb/t/innodb_bug60196-master.opt1
1 files changed, 1 insertions, 0 deletions
diff --git a/mysql-test/suite/innodb/t/innodb_bug60196-master.opt b/mysql-test/suite/innodb/t/innodb_bug60196-master.opt
new file mode 100755
index 00000000000..c0a1981fa7c
--- /dev/null
+++ b/mysql-test/suite/innodb/t/innodb_bug60196-master.opt
@@ -0,0 +1 @@
+--lower-case-table-names=2