summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorunknown <heikki@donna.mysql.fi>2001-11-23 01:21:42 +0200
committerunknown <heikki@donna.mysql.fi>2001-11-23 01:21:42 +0200
commit637622e322dab89db4314ebf33cdc8167e5bd938 (patch)
treefd406d6c4e16ead6e2c37c4c55700d59e110450e
parente585c81a869ddf4a1be91d04ef3d69f2e969dcb7 (diff)
downloadmariadb-git-637622e322dab89db4314ebf33cdc8167e5bd938.tar.gz
manual.texi:
Added foreign key def syntax + note that the check is not deferred to trx commit Docs/manual.texi: Added foreign key def syntax + note that the check is not deferred to trx commit
-rw-r--r--Docs/manual.texi8
1 files changed, 8 insertions, 0 deletions
diff --git a/Docs/manual.texi b/Docs/manual.texi
index ffa42d2ba73..d9e9d75876a 100644
--- a/Docs/manual.texi
+++ b/Docs/manual.texi
@@ -35283,6 +35283,12 @@ your job again, rather than wait for millions of disk i/os to complete.
InnoDB version 3.23.44 features foreign key constraints. InnoDB is the
first MySQL table type which allows you to define foreign key
constraints to guard the integrity of your data.
+
+The syntax of a foreign key constraint definition in InnoDB:
+@example
+FOREIGN KEY (index_col_name, ...) REFERENCES table_name (index_col_name, ...)
+@end example
+
An example:
@example
@@ -35303,6 +35309,8 @@ The size and the signedness of integer types has to be same.
When doing foreign key checks InnoDB sets shared row
level locks on child or parent records it has to look at.
+InnoDB checks foreign key constraints immediately: the check
+is not deferred to transaction commit.
InnoDB allows you to drop any table even though that
would break the foreign key constraints which reference