summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorheikki@hundin.mysql.fi <>2002-10-02 20:54:21 +0300
committerheikki@hundin.mysql.fi <>2002-10-02 20:54:21 +0300
commitdba3868523674d9871de6444823ad6f869c7c69b (patch)
tree0333cb68e22011f4f6bd506394be7e483e27b395
parent89a61ccd0ac2c81d6d4e4ba8f3731324b48313b8 (diff)
downloadmariadb-git-dba3868523674d9871de6444823ad6f869c7c69b.tar.gz
manual.texi:
InnoDB does allow a foreign key constraint name to be specified
-rw-r--r--Docs/manual.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/Docs/manual.texi b/Docs/manual.texi
index e655c0c9a67..2d35dd5302c 100644
--- a/Docs/manual.texi
+++ b/Docs/manual.texi
@@ -39260,7 +39260,7 @@ constraints to guard the integrity of your data.
The syntax of a foreign key constraint definition in InnoDB:
@example
-FOREIGN KEY (index_col_name, ...)
+[CONSTRAINT symbol] FOREIGN KEY (index_col_name, ...)
REFERENCES table_name (index_col_name, ...)
[ON DELETE CASCADE | ON DELETE SET NULL]
@end example
@@ -39319,7 +39319,7 @@ Starting from version 3.23.50 InnoDB allows you to add a new
foreign key constraint to a table through
@example
ALTER TABLE yourtablename
- ADD CONSTRAINT FOREIGN KEY (...) REFERENCES anothertablename(...)
+ADD [CONSTRAINT symbol] FOREIGN KEY (...) REFERENCES anothertablename(...)
@end example
Remember to create the required indexes first, though.