Foreign key constraints are a key part of database design, ensuring that relationships between tables are consistent and reliable. They create a relationship between two tables, ensuring that data matches across them. For example, a column in an “Orders” table (like CustomerID) might reference a column in a “Customers” table. This guarantees that every order belongs to a valid customer.
In earlier versions of SQL systems, defining foreign key constraints often required separate ALTER TABLE statements after the table was created:
CREATE TABLE Orders (
OrderID INT PRIMARY KEY,
CustomerID INT NOT NULL,
OrderDate DATE
);
ALTER TABLE Orders
ADD CONSTRAINT FK_Customer FOREIGN KEY (CustomerID)
REFERENCES Customers(CustomerID);
This two-step process was prone to errors and required careful management to ensure all constraints were applied correctly.
Inline Foreign Key Constraints
Most of the popular SQL database systems – PostgreSQL, Oracle, SQL Server, and MySQL since version 9.0, released in July 2024 – now support inline foreign key constraints. This means you can define the relationship directly in the column definition, making table creation easier to read:
CREATE TABLE Orders (
OrderID INT PRIMARY KEY,
CustomerID INT NOT NULL REFERENCES Customers(CustomerID),
OrderDate DATE
);
Fortunately, this syntax is the same across these systems. However, MySQL 9 additionally supports implicit foreign key constraints:
CREATE TABLE Orders (
OrderID INT PRIMARY KEY,
CustomerID INT NOT NULL REFERENCES Customers,
OrderDate DATE
);
By leaving out the (CustomerID) in the REFERENCES clause it will assume that you want to reference the primary key of the parent table. This syntax is unique to MySQL, and you should avoid it if you need to write SQL DDL statements that works across multiple database systems.
Schneide Blog 