diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2022-02-17 10:48:24 +0200 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2022-02-17 10:48:24 +0200 |
| commit | 73c391afc5f9315658e0486a375dbce2d109b9b5 (patch) | |
| tree | b5cff77840f7226d065292e4e0d471c6e07cbcee /storage | |
| parent | da64e503fb8715df1c592cf82c657be49bbfcd78 (diff) | |
| download | mariadb-git-73c391afc5f9315658e0486a375dbce2d109b9b5.tar.gz | |
MDEV-27583 InnoDB uses different constants for FK cascade error message in SQL vs error log
convert_error_code_to_mysql(): Use the correct limit FK_MAX_CASCADE_DEL
in the error message. The DICT_FK_MAX_RECURSIVE_LOAD applies to
the number of foreign key constraints in table definitions,
not to the number of rows that are visited while processing
a foreign key constraint.
Diffstat (limited to 'storage')
| -rw-r--r-- | storage/innobase/handler/ha_innodb.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/storage/innobase/handler/ha_innodb.cc b/storage/innobase/handler/ha_innodb.cc index a36ed4ddbcd..0c0900bd744 100644 --- a/storage/innobase/handler/ha_innodb.cc +++ b/storage/innobase/handler/ha_innodb.cc @@ -1953,7 +1953,7 @@ convert_error_code_to_mysql( "constraints that exceed max " "depth of %d. Please " "drop extra constraints and try " - "again", DICT_FK_MAX_RECURSIVE_LOAD); + "again", FK_MAX_CASCADE_DEL); return(HA_ERR_FK_DEPTH_EXCEEDED); case DB_CANT_CREATE_GEOMETRY_OBJECT: |