summaryrefslogtreecommitdiff
path: root/Docs
diff options
context:
space:
mode:
authorheikki@hundin.mysql.fi <>2002-10-02 20:44:44 +0300
committerheikki@hundin.mysql.fi <>2002-10-02 20:44:44 +0300
commit89a61ccd0ac2c81d6d4e4ba8f3731324b48313b8 (patch)
tree8bb0a3f3bd45b12bca4ce965c3d7acb28d1ff549 /Docs
parent12e170e630de552931afa1a9675c7a06e415be24 (diff)
downloadmariadb-git-89a61ccd0ac2c81d6d4e4ba8f3731324b48313b8.tar.gz
manual.texi:
InnoDB does allow a foreign key constraint name to be specified, though it is not used in any way
Diffstat (limited to 'Docs')
-rw-r--r--Docs/manual.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/Docs/manual.texi b/Docs/manual.texi
index 3875bfd0646..e655c0c9a67 100644
--- a/Docs/manual.texi
+++ b/Docs/manual.texi
@@ -36607,7 +36607,7 @@ deleted due to duplication of unique key values.
The @code{FOREIGN KEY}, @code{CHECK}, and @code{REFERENCES} clauses don't
actually do anything, except for InnoDB type tables which support
@code{ADD CONSTRAINT FOREIGN KEY (...) REFERENCES ... (...)}.
-Note that InnoDB does not allow a constraint @code{symbol} or @code{index_name}
+Note that InnoDB does not allow an @code{index_name}
to be specified. @xref{InnoDB}.
The syntax for other table types is provided only for compatibility,
to make it easier to port code from other SQL servers and to run applications