Foreign key linking mental model in SQL

Introduction

A foreign key connects two tables by linking a column in one table to a column in another. This helps keep data organized and related.

When you want to connect customer orders to the customers who made them.

When you need to link employees to the departments they work in.

When tracking which books belong to which authors in a library database.

When ensuring that product reviews are tied to existing products.

When you want to prevent deleting a record that is still used in another table.

Syntax

SQL

CREATE TABLE ChildTable (
  id INT PRIMARY KEY,
  parent_id INT,
  FOREIGN KEY (parent_id) REFERENCES ParentTable(id)
);

The foreign key column (parent_id) must match the data type of the referenced column (id).

The referenced column is usually a primary key in the parent table.

Examples

This links each order to a customer by customer_id.

SQL

CREATE TABLE Orders (
  order_id INT PRIMARY KEY,
  customer_id INT,
  FOREIGN KEY (customer_id) REFERENCES Customers(customer_id)
);

Each employee is linked to a department.

SQL

CREATE TABLE Employees (
  emp_id INT PRIMARY KEY,
  dept_id INT,
  FOREIGN KEY (dept_id) REFERENCES Departments(dept_id)
);

Adds a foreign key to an existing Reviews table linking to Products.

SQL

ALTER TABLE Reviews
ADD CONSTRAINT fk_product
FOREIGN KEY (product_id) REFERENCES Products(product_id);

Sample Program

This example creates two tables, Authors and Books, linked by author_id. It inserts authors and books, then shows book titles with their authors.

SQL

CREATE TABLE Authors (
  author_id INT PRIMARY KEY,
  name VARCHAR(100)
);

CREATE TABLE Books (
  book_id INT PRIMARY KEY,
  title VARCHAR(100),
  author_id INT,
  FOREIGN KEY (author_id) REFERENCES Authors(author_id)
);

INSERT INTO Authors VALUES (1, 'Jane Austen');
INSERT INTO Authors VALUES (2, 'Mark Twain');

INSERT INTO Books VALUES (101, 'Pride and Prejudice', 1);
INSERT INTO Books VALUES (102, 'Adventures of Huckleberry Finn', 2);

SELECT Books.title, Authors.name FROM Books
JOIN Authors ON Books.author_id = Authors.author_id;

Important Notes

Foreign keys help keep data consistent by preventing invalid links.

Trying to insert a child record with a non-existing parent_id will cause an error.

Deleting a parent record that has children may be blocked or cascade depending on settings.

Summary

Foreign keys connect tables by linking columns.

They keep data organized and prevent mistakes.

They are essential for relational database design.

Practice

1. What is the main purpose of a foreign key in a database?

easy

A. To link one table to another and ensure data consistency

B. To store large amounts of text data

C. To speed up database queries

D. To create a backup of the database

Solution

1. Step 1: Understand the role of foreign keys

   A foreign key connects one table to another by referencing a primary key in the related table.

2. Step 2: Identify the purpose of this connection

   This connection helps keep data consistent and organized by preventing invalid data entries.

3. Final Answer:

   To link one table to another and ensure data consistency -> Option A

4. Quick Check:

   Foreign key = link tables + data consistency [OK]

Hint: Foreign keys link tables to keep data correct [OK]

Common Mistakes:

• Thinking foreign keys store data themselves
• Confusing foreign keys with indexes
• Believing foreign keys speed up queries directly

2. Which of the following is the correct syntax to declare a foreign key in SQL?

easy

A. FOREIGN KEY column_name REFERENCES other_table

B. PRIMARY KEY (column_name) REFERENCES other_table(other_column)

C. FOREIGN KEY (column_name) REFERENCES other_table(other_column)

D. KEY FOREIGN (column_name) REFERENCES other_table(other_column)

Solution

1. Step 1: Recall the standard foreign key syntax

   The correct syntax includes the keywords FOREIGN KEY, the column in parentheses, then REFERENCES followed by the referenced table and column in parentheses.

2. Step 2: Compare options to syntax

   FOREIGN KEY (column_name) REFERENCES other_table(other_column) matches the correct syntax exactly. Other options have wrong keyword order or missing parentheses.

3. Final Answer:

   FOREIGN KEY (column_name) REFERENCES other_table(other_column) -> Option C

4. Quick Check:

   FOREIGN KEY + REFERENCES + (table.column) = A [OK]

Hint: FOREIGN KEY (col) REFERENCES table(col) is correct syntax [OK]

Common Mistakes:

• Omitting parentheses around column names
• Swapping PRIMARY KEY with FOREIGN KEY
• Incorrect keyword order

3. Given these tables:
CREATE TABLE Authors (AuthorID INT PRIMARY KEY, Name VARCHAR(50));
CREATE TABLE Books (BookID INT PRIMARY KEY, Title VARCHAR(100), AuthorID INT, FOREIGN KEY (AuthorID) REFERENCES Authors(AuthorID));
What happens if you try to insert INSERT INTO Books (BookID, Title, AuthorID) VALUES (1, 'My Book', 99); when there is no author with AuthorID = 99 in Authors?

medium

A. The insert succeeds but AuthorID is set to NULL

B. The insert fails due to foreign key constraint violation

C. The database creates a new author with AuthorID 99 automatically

D. The insert succeeds and adds the book

Solution

1. Step 1: Understand foreign key constraint behavior

   A foreign key requires that the referenced value exists in the parent table to maintain data integrity.

2. Step 2: Apply this to the insert statement

   Since AuthorID 99 does not exist in Authors, the insert violates the foreign key constraint and fails.

3. Final Answer:

   The insert fails due to foreign key constraint violation -> Option B

4. Quick Check:

   Foreign key requires existing parent row = D [OK]

Hint: Foreign key insert fails if parent key missing [OK]

Common Mistakes:

• Assuming automatic creation of missing parent rows
• Thinking insert will succeed with NULL foreign key
• Ignoring foreign key constraints

4. Consider this table creation:
CREATE TABLE Orders (OrderID INT PRIMARY KEY, CustomerID INT, FOREIGN KEY CustomerID REFERENCES Customers(CustomerID));
What is wrong with this statement?

medium

A. Foreign key cannot reference Customers table

B. CustomerID should be declared as PRIMARY KEY

C. PRIMARY KEY must be declared after FOREIGN KEY

D. Missing parentheses around the foreign key column name

Solution

1. Step 1: Check foreign key syntax

   The foreign key column name must be enclosed in parentheses after FOREIGN KEY.

2. Step 2: Identify the error in the statement

   The statement uses FOREIGN KEY CustomerID without parentheses, which is invalid syntax.

3. Final Answer:

   Missing parentheses around the foreign key column name -> Option D

4. Quick Check:

   FOREIGN KEY (col) needs parentheses [OK]

Hint: Always use parentheses around foreign key columns [OK]

Common Mistakes:

• Omitting parentheses in FOREIGN KEY declaration
• Misordering PRIMARY and FOREIGN KEY declarations
• Confusing foreign key with primary key requirements

5. You have two tables:
CREATE TABLE Departments (DeptID INT PRIMARY KEY, DeptName VARCHAR(50));
CREATE TABLE Employees (EmpID INT PRIMARY KEY, EmpName VARCHAR(50), DeptID INT, FOREIGN KEY (DeptID) REFERENCES Departments(DeptID) ON DELETE SET NULL);
If a department is deleted, what happens to employees linked to that department?

hard

A. Their DeptID is set to NULL automatically

B. The delete is blocked and fails

C. Employees linked to that department are deleted

D. Nothing happens; DeptID remains unchanged

Solution

1. Step 1: Understand ON DELETE SET NULL behavior

   This option means when the referenced row is deleted, the foreign key column in dependent rows is set to NULL.

2. Step 2: Apply to Employees and Departments

   Deleting a department sets DeptID to NULL in Employees who referenced it, keeping employees but removing the link.

3. Final Answer:

   Their DeptID is set to NULL automatically -> Option A

4. Quick Check:

   ON DELETE SET NULL means foreign keys become NULL [OK]

Hint: ON DELETE SET NULL clears foreign keys on delete [OK]

Common Mistakes:

• Assuming delete blocks or cascades employees
• Thinking employees get deleted automatically
• Ignoring ON DELETE action effects