manual.texi:

  InnoDB does allow a foreign key constraint name to be specified, though it is not used in any way
parent 12e170e6
...@@ -36607,7 +36607,7 @@ deleted due to duplication of unique key values. ...@@ -36607,7 +36607,7 @@ deleted due to duplication of unique key values.
The @code{FOREIGN KEY}, @code{CHECK}, and @code{REFERENCES} clauses don't The @code{FOREIGN KEY}, @code{CHECK}, and @code{REFERENCES} clauses don't
actually do anything, except for InnoDB type tables which support actually do anything, except for InnoDB type tables which support
@code{ADD CONSTRAINT FOREIGN KEY (...) REFERENCES ... (...)}. @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}. to be specified. @xref{InnoDB}.
The syntax for other table types is provided only for compatibility, 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 to make it easier to port code from other SQL servers and to run applications
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment