diff options
| author | unknown <arjen@co3064164-a.bitbike.com> | 2001-11-02 12:36:49 +1000 |
|---|---|---|
| committer | unknown <arjen@co3064164-a.bitbike.com> | 2001-11-02 12:36:49 +1000 |
| commit | 385213926452f80943770515437e2aa8f8867d14 (patch) | |
| tree | 801ec1d425a5ebf673c433f415784038b92da869 | |
| parent | 230d1df38eb867659fc8b6dda0e863819cced295 (diff) | |
| download | mariadb-git-385213926452f80943770515437e2aa8f8867d14.tar.gz | |
Fixed foreign key text/reference in "common queries" section.
| -rw-r--r-- | Docs/manual.texi | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/Docs/manual.texi b/Docs/manual.texi index 5f4e55855df..3a8d40168ed 100644 --- a/Docs/manual.texi +++ b/Docs/manual.texi @@ -14909,10 +14909,14 @@ select * from shop where price=@@min_price or price=@@max_price; @cindex foreign keys @cindex keys, foreign -You don't need foreign keys to join 2 tables. +In MySQL 3.23.44 and up, @code{InnoDB} tables supports checking of +foreign key constraints. @xref{InnoDB}. +See also @ref{example-Foreign keys}. -The only thing MySQL doesn't do is @code{CHECK} to make sure that -the keys you use really exist in the table(s) you're referencing and it +You don't actually need foreign keys to join 2 tables. +The only thing MySQL currently doesn't do (in type types other than +@code{InnoDB}), is @code{CHECK} to make sure that the keys you use +really exist in the table(s) you're referencing and it doesn't automatically delete rows from a table with a foreign key definition. If you use your keys like normal, it'll work just fine: |