Detailed explanation of MySQL foreign key constraints

Detailed explanation of MySQL foreign key constraints

Official documentation:
https://dev.mysql.com/doc/refman/5.7/en/create-table-foreign-keys.html

1. Foreign key function:

MySQL uses foreign key constraints to ensure the integrity and accuracy of data between tables.

2. Conditions for using foreign keys

  • Both tables must be InnoDB tables. MyISAM tables do not support foreign keys for the time being (it is said that future versions may support it, but at least it is not supported at present)
  • The foreign key column must have an index created. MySQL 4.1.2 and later versions will automatically create an index when creating a foreign key, but if you use an earlier version, you need to create an index explicitly.
  • The columns of the two tables in the foreign key relationship must have similar data types, that is, columns that can be converted to each other, such as int and tinyint, but not int and char.

3. Create Grammar

[CONSTRAINT [symbol]] FOREIGN KEY
[index_name] (col_name, ...)
REFERENCES tbl_name (col_name,...)
[ON DELETE reference_option]
[ON UPDATE reference_option]

reference_option:
RESTRICT | CASCADE | SET NULL | NO ACTION | SET DEFAULT

This syntax can be used in CREATE TABLE and ALTER TABLE. If you do not specify the CONSTRAINT symbol, MYSQL will automatically generate a name.
ON DELETE and ON UPDATE indicate event triggering restrictions, and you can set parameters:
RESTRICT (restrict changes to foreign keys in foreign tables)
CASCADE (follow foreign key changes)
SET NULL
SET DEFAULT (Set the default value)
NO ACTION (no action, default)

CASCADE: Indicates that when the parent table is updated or deleted, the corresponding records in the child table are updated or deleted.
RESTRICT and NO ACTION: When the child table has related records, the parent table cannot be deleted or updated independently.
SET NULL: Indicates that when the parent table is updated or deleted, the corresponding fields of the child table are set to NULL

4. Case Demonstration

CASCADE constraint mode

1. Create the power table (parent table) country
create table country (
id int not null,
name varchar(30),
primary key(id)
);

2. Insert records insert into country values(1,'Western Europe');
insert into country values(2,'Maya');
insert into country values(3,'Sicily');

3. Create a arms table (sub-table) and establish constraints create table solider (
id int not null,
name varchar(30),
country_id int,
primary key(id),
foreign key(country_id) references country(id) on delete cascade on update cascade,
);

4. Reference integrity test insert into solider values(1,'Western European trainee infantry',1);
#insert successfully insert into solider values(2,'Maya short spearman',2);
#insert successfully insert into solider values(3,'Sicily Norman Knights',3)
#insert successfullyinsert into solider values(4,'French Swordsman',4);
#Insert failed because there is no faction with id 4 in the country table. 5. Constraint method test insert into solider values(4, 'Maya Tiger Warriors', 2);
#Successfully inserted delete from country where id=2;
#This will cause the records with id 2 and 4 in the solider table to be deleted at the same time, because this faction no longer exists in the parent table, so the corresponding arms will naturally disappear update country set id=8 where id=1;
#As a result, all records in the solider table with country_id 1 will also be modified to 8

With SET NULL constraint

1. Create a soldier table (sub-table) and establish a constraint relationship drop table if exists solider;
create table solider(
id int not null,
name varchar(30),
country_id int,
primary key(id),
foreign key(country_id) references country(id) on delete set null on update set null,
);

2. Reference integrity test insert into solider values(1,'Western European trainee infantry',1);
#insert successfully insert into solider values(2,'Maya short spearman',2);
#insert successfully insert into solider values(3,'Sicily Norman Knights',3)
#insert successfullyinsert into solider values(4,'French Swordsman',4);
#Insert failed because there is no faction with id 4 in the country table. 3. Constraint method test insert into solider values ​​(4, 'Sicilian Archer', 3);
#Successfully inserted delete from country where id=3;
#This will cause the records with id 3 and 4 in the solider table to be set to NULL
update country set id=8 where id=1;
# Causes all records in the solider table where country_id is 1 to be set to NULL

With NO ACTION or RESTRICT mode (default)

1. Create a soldier table (sub-table) and establish a constraint relationship drop table if exists solider;
create table solider(
id int not null,
name varchar(30),
country_id int,
primary key(id),
foreign key(country_id) references country(id) on delete RESTRICT on update RESTRICT,
);

2. Reference integrity test insert into solider values(1,'Western European trainee infantry',1);
#insert successfully insert into solider values(2,'Maya short spearman',2);
#insert successfully insert into solider values(3,'Sicily Norman Knights',3)
#insert successfullyinsert into solider values(4,'French Swordsman',4);
#Insert failed because there is no faction with id 4 in the country table 3. Constraint method test insert into solider values(4, 'Western European Knights', 1);
#Successfully inserted delete from country where id=1;
#An error occurred. There are related records in the child table, so the corresponding records in the parent table cannot be deleted. That is, the arms table also has arms belonging to Western Europe, so the Western European forces in the parent table cannot be deleted alone. update country set id=8 where id=1;
#Error, there are related records in the child table, so the parent table cannot be modified

The above is the detailed explanation of MySQL foreign key constraints. For more information about MySQL foreign key constraints, please pay attention to other related articles on 123WORDPRESS.COM!

You may also be interested in:
  • Specific method to add foreign key constraints in mysql
  • MySQL foreign key constraint (FOREIGN KEY) case explanation
  • Summary of MySQL foreign key constraints and table relationships
  • Example explanation of MySQL foreign key constraints
  • Introduction to MySQL method of deleting table data with foreign key constraints
  • Simple implementation of ignoring foreign key constraints when deleting MySQL tables
  • How to disable foreign key constraint checking in MySQL child tables
  • How to create and delete foreign key constraints in MySQL

<<:  Detailed tutorial on installing CUDA9.0 on Ubuntu16.04

>>:  Detailed explanation of vue.js dynamic components

Recommend

Use Navicate to connect to MySQL on Alibaba Cloud Server

1. First enter the server's mysql to modify p...

Detailed analysis of GUID display issues in Mongodb

Find the problem I recently migrated the storage ...

Can you do all the web page making test questions?

Web page design related questions, see if you can...

JavaScript - Using slots in Vue: slot

Table of contents Using slots in Vue: slot Scoped...

Example code for implementing an Upload component using Vue3

Table of contents General upload component develo...

Comprehensive explanation of CocosCreator hot update

Table of contents Preface What is Hot Change Coco...

Let the web page redirect to other pages after opening for a few seconds

Just add the following code to achieve it. Method ...

Does MySql need to commit?

Whether MySQL needs to commit when performing ope...

How to install and configure GitLab on Ubuntu 20.04

introduce GitLab CE or Community Edition is an op...

Implementation steps of vue-element-admin to build a backend management system

Recently, when I was working on a conference heal...

Linux concurrent execution is simple, just do it this way

Concurrency Functions time for i in `grep server ...

MySQL sharding details

1. Business scenario introduction Suppose there i...

JavaScript canvas to achieve mirror image effect

This article shares the specific code for JavaScr...

Don’t bother with JavaScript if you can do it with CSS

Preface Any application that can be written in Ja...

A brief talk about cloning JavaScript

Table of contents 1. Shallow cloning 2. Deep clon...