Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
MariaDB
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
MariaDB
Commits
0f5d7bcb
Commit
0f5d7bcb
authored
Nov 23, 2001
by
heikki@donna.mysql.fi
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
manual.texi:
Added foreign key def syntax + note that the check is not deferred to trx commit
parent
7f5f58dc
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
0 deletions
+8
-0
Docs/manual.texi
Docs/manual.texi
+8
-0
No files found.
Docs/manual.texi
View file @
0f5d7bcb
...
@@ -35283,6 +35283,12 @@ your job again, rather than wait for millions of disk i/os to complete.
...
@@ -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
InnoDB version 3.23.44 features foreign key constraints. InnoDB is the
first MySQL table type which allows you to define foreign key
first MySQL table type which allows you to define foreign key
constraints to guard the integrity of your data.
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:
An example:
@example
@example
...
@@ -35303,6 +35309,8 @@ The size and the signedness of integer types has to be same.
...
@@ -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
When doing foreign key checks InnoDB sets shared row
level locks on child or parent records it has to look at.
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
InnoDB allows you to drop any table even though that
would break the foreign key constraints which reference
would break the foreign key constraints which reference
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment