summaryrefslogtreecommitdiff
path: root/storage
diff options
context:
space:
mode:
authorAnnamalai Gurusami <annamalai.gurusami@oracle.com>2013-03-28 10:25:23 +0530
committerAnnamalai Gurusami <annamalai.gurusami@oracle.com>2013-03-28 10:25:23 +0530
commitefff966148b22090a2475ddaabd30a08ddbda367 (patch)
tree1b5495f8afd11749c8a89d24deaa133957d89d23 /storage
parent0cbb7ddcd63b20783387ca85fbfa5adcc7d4437b (diff)
parent38e97daee12c3aac91ff83c2577f9a678c47d27c (diff)
downloadmariadb-git-efff966148b22090a2475ddaabd30a08ddbda367.tar.gz
Merge from mysql-5.1 to mysql-5.5
Diffstat (limited to 'storage')
-rw-r--r--storage/innobase/include/dict0mem.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/storage/innobase/include/dict0mem.h b/storage/innobase/include/dict0mem.h
index 15b53a45afa..5c7d492dbbb 100644
--- a/storage/innobase/include/dict0mem.h
+++ b/storage/innobase/include/dict0mem.h
@@ -127,7 +127,7 @@ This could result in rescursive calls and out of stack error eventually.
DICT_FK_MAX_RECURSIVE_LOAD defines the maximum number of recursive loads,
when exceeded, the child table will not be loaded. It will be loaded when
the foreign constraint check needs to be run. */
-#define DICT_FK_MAX_RECURSIVE_LOAD 255
+#define DICT_FK_MAX_RECURSIVE_LOAD 30
/** Similarly, when tables are chained together with foreign key constraints
with on cascading delete/update clause, delete from parent table could