Self join concept in SQL - Step-by-Step Execution

Concept Flow - Self join concept

Start with one table

↓

Create two aliases of the same table

↓

Join the table aliases on a related column

↓

Filter or select matching rows

↓

Return combined rows showing relationships within the same table

A self join uses one table twice by giving it two names (aliases) and joining it to itself to find related rows.

Execution Sample

SQL

SELECT e1.name AS Employee, e2.name AS Manager
FROM employees e1
JOIN employees e2 ON e1.manager_id = e2.id;

This query finds each employee and their manager by joining the employees table to itself.

Execution Table

Step	Action	e1.name	e1.manager_id	e2.id	e2.name	Join Condition (e1.manager_id = e2.id)	Output Row
1	Start with first employee row	Alice	2	2	Bob	2 = 2 (True)	Alice, Bob
2	Next employee row	Charlie	3	2	Bob	3 = 2 (False)
3	Check next manager row	Charlie	3	3	David	3 = 3 (True)	Charlie, David
4	Next employee row	Eve	2	2	Bob	2 = 2 (True)	Eve, Bob
5	Next employee row	Frank	4	2	Bob	4 = 2 (False)
6	Check next manager row	Frank	4	3	David	4 = 3 (False)
7	Check next manager row	Frank	4	4	Grace	4 = 4 (True)	Frank, Grace
8	No more rows						End of join

💡 All employee rows checked against all manager rows; join condition false or true determines output.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	After 6	After 7	Final
e1.name	Alice	Charlie	Charlie	Eve	Frank	Frank	Frank	Frank
e1.manager_id	2	3	3	2	4	4	4	4
e2.id	2	2	3	2	2	3	4	4
e2.name	Bob	Bob	David	Bob	Bob	David	Grace	Grace

Key Moments - 3 Insights

Why do we need to use aliases like e1 and e2 in a self join?

Because we use the same table twice in the query, aliases help SQL know which copy we mean. See execution_table rows where e1 and e2 columns differ.

How does the join condition work when joining a table to itself?

The join condition compares columns from the two aliases. For example, e1.manager_id = e2.id matches employees to their managers, as shown in the join condition column in execution_table.

What happens if the join condition is false for some rows?

Those rows do not appear in the output. For example, in execution_table rows 2, 5, and 6 the condition is false, so no output row is produced.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output row at step 3?

A Charlie, David

B Alice, Bob

C Eve, Bob

D Frank, Grace

💡 Hint

Check the Output Row column in execution_table at step 3.

At which step does the join condition first become false?

A Step 5

B Step 2

C Step 4

D Step 7

💡 Hint

Look at the Join Condition column in execution_table for the first 'False' value.

If we changed the join condition to e1.id = e2.manager_id, what would happen?

A It would find employees with no managers.

B It would cause a syntax error.

C It would find managers and their employees instead.

D It would return the same results.

💡 Hint

Think about reversing the join condition and how it changes the relationship direction.

Concept Snapshot

Self join uses one table twice by giving it two aliases.
Join the aliases on related columns within the same table.
Useful to find relationships like employee-manager in one table.
Syntax: FROM table AS t1 JOIN table AS t2 ON t1.col = t2.col
Output combines rows from the same table based on the join condition.

Full Transcript

A self join means joining a table to itself. We do this by giving the table two different names called aliases. Then we join these aliases on columns that relate rows inside the same table. For example, to find each employee's manager, we join the employees table to itself where the employee's manager_id matches the manager's id. The execution table shows step-by-step how each employee row is matched with manager rows. When the join condition is true, the pair appears in the output. When false, it does not. Aliases are important to tell SQL which copy of the table we mean. Changing the join condition changes the relationship direction we find. This concept helps find relationships inside one table using SQL.

Practice

1. What is the main purpose of a self join in SQL?

easy

A. To combine rows from two tables without any condition

B. To join two different tables based on a common column

C. To join a table to itself to compare rows within the same table

D. To delete duplicate rows from a table

Solution

1. Step 1: Understand the concept of self join

   A self join is used when you want to compare rows within the same table by treating it as two separate tables using aliases.

2. Step 2: Identify the correct purpose

   Joining a table to itself allows you to find relationships or comparisons between rows in the same table, such as hierarchical data or pairs.

3. Final Answer:

   To join a table to itself to compare rows within the same table -> Option C

4. Quick Check:

   Self join = join table to itself [OK]

Hint: Self join means joining table to itself using aliases [OK]

Common Mistakes:

• Confusing self join with joining two different tables
• Thinking self join deletes duplicates
• Assuming self join combines rows without condition

2. Which of the following is the correct syntax to perform a self join on a table named employees with alias e1 and e2?

easy

A. SELECT * FROM employees e1 JOIN employees e2 ON e1.id = e2.manager_id;

B. SELECT * FROM employees JOIN employees ON id = manager_id;

C. SELECT * FROM employees e1, employees e2 ON e1.id = e2.manager_id;

D. SELECT * FROM employees e1 INNER JOIN employees e2 ON e1.id = e2.id;

Solution

1. Step 1: Use table aliases for self join

   To join a table to itself, you must use aliases like e1 and e2 to distinguish the two instances.

2. Step 2: Write the join condition correctly

   The join condition should relate columns from the two aliases, for example e1.id = e2.manager_id to find employees and their managers.

3. Final Answer:

   SELECT * FROM employees e1 JOIN employees e2 ON e1.id = e2.manager_id; -> Option A

4. Quick Check:

   Self join syntax = table alias + join condition [OK]

Hint: Always use aliases to distinguish the same table twice [OK]

Common Mistakes:

• Not using aliases causes syntax errors
• Joining on wrong columns returns wrong results
• Using comma join without aliases is confusing

3. Given the table employees with columns id, name, and manager_id, what will this query return?

SELECT e1.name AS Employee, e2.name AS Manager FROM employees e1 LEFT JOIN employees e2 ON e1.manager_id = e2.id;

medium

A. Syntax error due to missing WHERE clause

B. List of employees with their managers' names, NULL if no manager

C. List of employees without managers only

D. List of managers with their employees' names

Solution

1. Step 1: Understand the LEFT JOIN on self join

   The query joins the employees table to itself using aliases e1 and e2, matching e1.manager_id to e2.id to find each employee's manager.

2. Step 2: Interpret the SELECT columns and join type

   Using LEFT JOIN means all employees (e1) appear, even if they have no manager (e2.name will be NULL). The SELECT shows employee and manager names.

3. Final Answer:

   List of employees with their managers' names, NULL if no manager -> Option B

4. Quick Check:

   LEFT JOIN self join shows all employees with managers [OK]

Hint: LEFT JOIN keeps all employees, shows NULL for missing managers [OK]

Common Mistakes:

• Confusing employee and manager columns
• Thinking it lists only managers or only employees without managers
• Assuming syntax error without WHERE clause

4. Identify the error in this self join query:

SELECT e1.name, e2.name FROM employees e1 JOIN employees e2 ON e1.id = e2.id;

medium

A. Missing table aliases for employees

B. Using JOIN instead of LEFT JOIN causes error

C. Syntax error due to missing WHERE clause

D. The join condition compares the same column, causing incorrect results

Solution

1. Step 1: Analyze the join condition

   The query joins employees to itself on e1.id = e2.id, which matches each row to itself only, not to related rows.

2. Step 2: Understand the effect of the condition

   This join condition does not find relationships like manager or pairs; it just duplicates rows, which is likely incorrect for self join use.

3. Final Answer:

   The join condition compares the same column, causing incorrect results -> Option D

4. Quick Check:

   Self join needs meaningful join condition, not same column equals [OK]

Hint: Join condition must relate different columns for meaningful self join [OK]

Common Mistakes:

• Joining on identical columns returns only same rows
• Forgetting to use aliases
• Assuming JOIN requires WHERE clause

5. You have a table employees with columns id, name, and manager_id. Write a query using self join to find all employees who share the same manager. Which query correctly achieves this?

hard

A. SELECT e1.name, e2.name FROM employees e1 JOIN employees e2 ON e1.manager_id = e2.manager_id WHERE e1.id <> e2.id;

B. SELECT e1.name, e2.name FROM employees e1 JOIN employees e2 ON e1.id = e2.manager_id;

C. SELECT e1.name, e2.name FROM employees e1 JOIN employees e2 ON e1.manager_id = e2.id WHERE e1.id = e2.id;

D. SELECT e1.name, e2.name FROM employees e1 JOIN employees e2 ON e1.manager_id = e2.manager_id WHERE e1.id = e2.id;

Solution

1. Step 1: Understand the goal

   We want pairs of employees who share the same manager, so their manager_id values must be equal but employees must be different.

2. Step 2: Write the self join condition

   Joining on e1.manager_id = e2.manager_id finds employees with the same manager. Adding WHERE e1.id <> e2.id excludes pairing an employee with themselves.

3. Final Answer:

   SELECT e1.name, e2.name FROM employees e1 JOIN employees e2 ON e1.manager_id = e2.manager_id WHERE e1.id <> e2.id; -> Option A

4. Quick Check:

   Same manager and different employees = SELECT e1.name, e2.name FROM employees e1 JOIN employees e2 ON e1.manager_id = e2.manager_id WHERE e1.id <> e2.id; [OK]

Hint: Join on manager_id and exclude same employee IDs [OK]

Common Mistakes:

• Joining on employee id instead of manager id
• Not excluding same employee pairs
• Using equality on employee IDs causing no pairs