FOREIGN KEY constraint in SQL - Mini Project: Build & Apply

Creating and Using FOREIGN KEY Constraint in SQL

📖 Scenario: You are building a simple database for a small bookstore. You want to keep track of books and their authors. Each book must be linked to an author to ensure data consistency.

🎯 Goal: Create two tables: Authors and Books. Use a FOREIGN KEY constraint in the Books table to link each book to an author in the Authors table.

📋 What You'll Learn

Create an Authors table with columns AuthorID (primary key) and Name.

Create a Books table with columns BookID (primary key), Title, and AuthorID.

Add a FOREIGN KEY constraint on AuthorID in the Books table referencing AuthorID in the Authors table.

💡 Why This Matters

🌍 Real World

Bookstores and many other businesses use foreign keys to keep related data connected and consistent.

💼 Career

Understanding foreign keys is essential for database design and ensuring data integrity in real-world applications.

1

Create the Authors table

Write a SQL statement to create a table called Authors with two columns: AuthorID as an integer primary key, and Name as a text field.

SQL

-- Create the Authors table with AuthorID and Name
-- Your code here

Hint

Use CREATE TABLE Authors and define AuthorID as INT PRIMARY KEY.

2

Create the Books table without foreign key

Write a SQL statement to create a table called Books with three columns: BookID as an integer primary key, Title as a text field, and AuthorID as an integer.

SQL

CREATE TABLE Authors (
    AuthorID INT PRIMARY KEY,
    Name TEXT
);
-- Create the Books table with BookID, Title, and AuthorID
-- Your code here

Hint

Define BookID as INT PRIMARY KEY, Title as TEXT, and AuthorID as INT.

3

Add FOREIGN KEY constraint to Books table

Modify the Books table creation statement to add a FOREIGN KEY constraint on AuthorID that references AuthorID in the Authors table.

SQL

CREATE TABLE Authors (
    AuthorID INT PRIMARY KEY,
    Name TEXT
);

-- Modify the Books table to add FOREIGN KEY constraint on AuthorID
CREATE TABLE Books (
    BookID INT PRIMARY KEY,
    Title TEXT,
    AuthorID INT,
    -- Your code here
);

Hint

Use FOREIGN KEY (AuthorID) REFERENCES Authors(AuthorID) inside the Books table definition.

4

Complete the database setup with both tables

Ensure the full SQL code includes the creation of both Authors and Books tables, with the FOREIGN KEY constraint on Books.AuthorID referencing Authors.AuthorID.

SQL

-- Confirm the full SQL code for both tables with FOREIGN KEY constraint
-- Your code here

Hint

Make sure both tables are created and the foreign key constraint is present in the Books table.

Practice

1. What is the main purpose of a FOREIGN KEY constraint in a database?

easy

A. To store large amounts of text data efficiently

B. To speed up database queries by creating indexes

C. To link two tables by ensuring values in one table match values in another

D. To automatically backup the database

Solution

1. Step 1: Understand the role of FOREIGN KEY

   A FOREIGN KEY connects columns in two tables to keep data related and consistent.

2. Step 2: Compare options with this role

   Only To link two tables by ensuring values in one table match values in another describes linking tables by matching values, which is the purpose of FOREIGN KEY.

3. Final Answer:

   To link two tables by ensuring values in one table match values in another -> Option C

4. Quick Check:

   FOREIGN KEY links tables = A [OK]

Hint: FOREIGN KEY links tables by matching columns [OK]

Common Mistakes:

• Confusing FOREIGN KEY with indexing
• Thinking FOREIGN KEY stores data
• Assuming FOREIGN KEY backs up data

2. Which of the following is the correct syntax to add a FOREIGN KEY constraint to an existing table Orders referencing Customers(CustomerID)?

easy

A. ALTER TABLE Orders ADD FOREIGN KEY (CustomerID) REFERENCES Customers(CustomerID);

B. ALTER TABLE Orders ADD PRIMARY KEY (CustomerID) REFERENCES Customers(CustomerID);

C. ALTER TABLE Orders ADD FOREIGN KEY CustomerID REFERENCES Customers(CustomerID);

D. ALTER TABLE Orders ADD FOREIGN KEY (CustomerID) TO Customers(CustomerID);

Solution

1. Step 1: Recall correct ALTER TABLE syntax for FOREIGN KEY

   The correct syntax uses: ALTER TABLE table_name ADD FOREIGN KEY (column) REFERENCES other_table(column);

2. Step 2: Check each option

   ALTER TABLE Orders ADD FOREIGN KEY (CustomerID) REFERENCES Customers(CustomerID); matches the correct syntax exactly. Options A, B, and C have syntax errors or wrong keywords.

3. Final Answer:

   ALTER TABLE Orders ADD FOREIGN KEY (CustomerID) REFERENCES Customers(CustomerID); -> Option A

4. Quick Check:

   Correct ALTER TABLE FOREIGN KEY syntax = D [OK]

Hint: Use ADD FOREIGN KEY (col) REFERENCES table(col) syntax [OK]

Common Mistakes:

• Using PRIMARY KEY instead of FOREIGN KEY
• Omitting parentheses around column name
• Using TO instead of REFERENCES keyword

3. Given these tables:
CREATE TABLE Customers (CustomerID INT PRIMARY KEY, Name VARCHAR(50));
CREATE TABLE Orders (OrderID INT PRIMARY KEY, CustomerID INT, FOREIGN KEY (CustomerID) REFERENCES Customers(CustomerID));
What happens if you try to insert INSERT INTO Orders (OrderID, CustomerID) VALUES (1, 999); when there is no customer with CustomerID = 999?

medium

A. The insert fails due to FOREIGN KEY constraint violation

B. The insert succeeds but CustomerID is set to NULL

C. The insert succeeds and adds the order with CustomerID 999

D. The insert succeeds but triggers a warning

Solution

1. Step 1: Understand FOREIGN KEY enforcement

   FOREIGN KEY requires the referenced value to exist in the parent table before inserting.

2. Step 2: Apply to the insert statement

   Since CustomerID 999 does not exist in Customers, the insert violates the FOREIGN KEY rule and fails.

3. Final Answer:

   The insert fails due to FOREIGN KEY constraint violation -> Option A

4. Quick Check:

   Insert with missing parent key = fails [OK]

Hint: Insert fails if referenced key doesn't exist [OK]

Common Mistakes:

• Assuming insert sets foreign key to NULL automatically
• Thinking insert triggers only warnings, not errors
• Believing insert succeeds without parent key

4. You have 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. PRIMARY KEY cannot be used with FOREIGN KEY in the same table

B. CustomerID must be declared as PRIMARY KEY

C. REFERENCES keyword is not allowed in FOREIGN KEY constraints

D. FOREIGN KEY must be declared with parentheses around the column name

Solution

1. Step 1: Check FOREIGN KEY syntax

   FOREIGN KEY columns must be enclosed in parentheses, like FOREIGN KEY (CustomerID).

2. Step 2: Identify the error in the statement

   The statement misses parentheses around CustomerID in FOREIGN KEY declaration, causing syntax error.

3. Final Answer:

   FOREIGN KEY must be declared with parentheses around the column name -> Option D

4. Quick Check:

   FOREIGN KEY columns need parentheses [OK]

Hint: Always use parentheses around FOREIGN KEY columns [OK]

Common Mistakes:

• Omitting parentheses around foreign key columns
• Thinking PRIMARY KEY conflicts with FOREIGN KEY
• Misunderstanding REFERENCES usage

5. You want to delete a customer from Customers table who has orders in Orders table. The Orders table has a FOREIGN KEY on CustomerID referencing Customers(CustomerID) with ON DELETE CASCADE. What will happen when you delete that customer?

hard

A. The delete fails because orders exist for that customer

B. The customer is deleted and all their orders are automatically deleted

C. The customer is deleted but orders remain with invalid CustomerID

D. The delete succeeds but sets CustomerID in orders to NULL

Solution

1. Step 1: Understand ON DELETE CASCADE effect

   ON DELETE CASCADE means deleting a parent row also deletes all related child rows automatically.

2. Step 2: Apply to deleting a customer with orders

   Deleting the customer will also delete all orders linked by CustomerID in Orders table.

3. Final Answer:

   The customer is deleted and all their orders are automatically deleted -> Option B

4. Quick Check:

   ON DELETE CASCADE deletes related rows [OK]

Hint: ON DELETE CASCADE removes child rows with parent [OK]

Common Mistakes:

• Assuming delete fails due to existing child rows
• Thinking child rows remain with broken references
• Confusing CASCADE with SET NULL behavior