LEFT JOIN vs RIGHT JOIN decision in SQL - Visual Side-by-Side Comparison

Concept Flow - LEFT JOIN vs RIGHT JOIN decision

Start with LEFT JOIN

↓

Include all rows from Left Table

↓

Match rows from Right Table

↓

If no match, fill Right Table columns with NULL

↓

Result: All Left Table rows + matched Right Table rows

↓

Start with RIGHT JOIN

↓

Include all rows from Right Table

↓

Match rows from Left Table

↓

If no match, fill Left Table columns with NULL

↓

Result: All Right Table rows + matched Left Table rows

LEFT JOIN keeps all rows from the left table, matching right table rows or NULLs; RIGHT JOIN keeps all rows from the right table, matching left table rows or NULLs.

Execution Sample

SQL

SELECT A.id, B.value
FROM A
LEFT JOIN B ON A.id = B.id;

This query returns all rows from table A, and matching rows from B; if no match, B columns are NULL.

Execution Table

Step	Action	Left Table Row	Right Table Row	Result Row	Notes
1	Take first row from A	A.id=1	Find B.id=1	1, B.value=100	Match found, include both
2	Take second row from A	A.id=2	Find B.id=2	2, B.value=NULL	No match in B, fill NULL
3	Take third row from A	A.id=3	Find B.id=3	3, B.value=300	Match found, include both
4	No more rows in A				LEFT JOIN ends after all A rows processed

💡 All rows from left table A processed; right table B matched or NULL filled

Variable Tracker

Variable	Start	After 1	After 2	After 3	Final
Current A row	None	id=1	id=2	id=3	None
Matched B row	None	id=1,value=100	None	id=3,value=300	None
Result row	None	(1,100)	(2,NULL)	(3,300)	All rows processed

Key Moments - 2 Insights

Why does the second result row have NULL for B.value?

Because in execution_table row 2, A.id=2 has no matching B.id=2, so LEFT JOIN fills B columns with NULL.

What happens if we switch to RIGHT JOIN?

The join would include all rows from B, matching A rows or NULL if no match, reversing the role of tables as shown in concept_flow.

Visual Quiz - 3 Questions

Look at the execution_table, what is the Result Row at Step 3?

A (3, NULL)

B (3, 300)

C (3, 100)

D (NULL, 300)

💡 Hint

Check execution_table row 3 under Result Row column

At which step does the LEFT JOIN fill NULL for the right table columns?

A Step 1

B Step 3

C Step 2

D No NULLs filled

💡 Hint

Look at execution_table row 2 Notes and Result Row

If we change the query to RIGHT JOIN, which table's rows will all appear in the result?

A Right table B

B Left table A

C Only matching rows

D No rows

💡 Hint

Refer to concept_flow description about RIGHT JOIN behavior

Concept Snapshot

LEFT JOIN returns all rows from the left table plus matched rows from the right table; unmatched right rows show NULL.
RIGHT JOIN returns all rows from the right table plus matched rows from the left table; unmatched left rows show NULL.
Use LEFT JOIN when you want to keep all left table data.
Use RIGHT JOIN when you want to keep all right table data.
Both joins match rows based on the ON condition.
If no match, columns from the other table are NULL.

Full Transcript

This visual execution shows how LEFT JOIN and RIGHT JOIN work in SQL. LEFT JOIN keeps all rows from the left table and matches rows from the right table. If no match is found, the right table columns are filled with NULL. The execution table traces each row from the left table, showing matches or NULLs. The variable tracker shows how the current rows and results change step-by-step. Key moments clarify why NULLs appear and what changes if we switch to RIGHT JOIN. The quiz tests understanding of the join results and behavior. The concept snapshot summarizes the key differences and when to use each join type.

Practice

1. Which JOIN type keeps all rows from the first (left) table, even if there is no matching row in the second (right) table?

easy

A. RIGHT JOIN

B. INNER JOIN

C. LEFT JOIN

D. FULL JOIN

Solution

1. Step 1: Understand LEFT JOIN behavior

   LEFT JOIN returns all rows from the first table and matching rows from the second table. If no match, NULLs appear for second table columns.

2. Step 2: Compare with RIGHT JOIN

   RIGHT JOIN keeps all rows from the second table, not the first. INNER JOIN only returns matching rows. FULL JOIN returns all rows from both tables.

3. Final Answer:

   LEFT JOIN -> Option C

4. Quick Check:

   LEFT JOIN keeps all left table rows [OK]

Hint: LEFT JOIN keeps all from first table, RIGHT JOIN from second [OK]

Common Mistakes:

• Confusing LEFT JOIN with RIGHT JOIN
• Thinking INNER JOIN keeps unmatched rows
• Assuming FULL JOIN keeps only one table's rows

2. Which of the following is the correct syntax to perform a RIGHT JOIN between tables Employees and Departments on Employees.DeptID = Departments.ID?

easy

A. SELECT * FROM Employees RIGHT JOIN Departments ON Employees.DeptID = Departments.ID;

B. SELECT * FROM Employees LEFT JOIN Departments ON Employees.DeptID = Departments.ID;

C. SELECT * FROM Employees RIGHT JOIN Departments WHERE Employees.DeptID = Departments.ID;

D. SELECT * FROM Employees JOIN Departments ON Employees.DeptID = Departments.ID;

Solution

1. Step 1: Check JOIN syntax correctness

   RIGHT JOIN requires ON clause to specify join condition. SELECT * FROM Employees RIGHT JOIN Departments ON Employees.DeptID = Departments.ID; uses correct syntax with ON clause.

2. Step 2: Identify errors in other options

   SELECT * FROM Employees LEFT JOIN Departments ON Employees.DeptID = Departments.ID; uses LEFT JOIN, not RIGHT JOIN. SELECT * FROM Employees RIGHT JOIN Departments WHERE Employees.DeptID = Departments.ID; uses WHERE instead of ON, which is incorrect for JOIN condition. SELECT * FROM Employees JOIN Departments ON Employees.DeptID = Departments.ID; uses JOIN without specifying LEFT or RIGHT, defaults to INNER JOIN.

3. Final Answer:

   SELECT * FROM Employees RIGHT JOIN Departments ON Employees.DeptID = Departments.ID; -> Option A

4. Quick Check:

   RIGHT JOIN needs ON clause [OK]

Hint: RIGHT JOIN syntax requires ON, not WHERE [OK]

Common Mistakes:

• Using WHERE instead of ON for join condition
• Confusing LEFT JOIN with RIGHT JOIN syntax
• Omitting JOIN type defaults to INNER JOIN

3. Given tables Authors and Books, what will be the result of this query?

SELECT Authors.Name, Books.Title FROM Authors LEFT JOIN Books ON Authors.ID = Books.AuthorID;

Assuming Authors has 3 rows and Books has 2 rows, with one author having no books, what will the output include?

medium

A. Only authors who have books, excluding authors without books

B. All 3 authors with their book titles; NULL for authors without books

C. All books with their authors; NULL for books without authors

D. All authors and all books, matched and unmatched

Solution

1. Step 1: Understand LEFT JOIN output

   LEFT JOIN keeps all rows from Authors (left table). For authors without matching books, Books.Title will be NULL.

2. Step 2: Analyze given data

   Authors has 3 rows, Books has 2 rows. One author has no books, so that author appears with NULL for book title.

3. Final Answer:

   All 3 authors with their book titles; NULL for authors without books -> Option B

4. Quick Check:

   LEFT JOIN keeps all left rows, fills NULLs for no match [OK]

Hint: LEFT JOIN keeps all left rows, unmatched right columns are NULL [OK]

Common Mistakes:

• Thinking unmatched left rows are excluded
• Confusing LEFT JOIN with INNER JOIN
• Assuming unmatched right rows appear in LEFT JOIN

4. You wrote this query but it returns fewer rows than expected:

SELECT * FROM Orders RIGHT JOIN Customers ON Orders.CustomerID = Customers.ID;

What is the likely mistake?

medium

A. Using ON instead of WHERE for join condition

B. Missing WHERE clause to filter rows

C. Not specifying table aliases

D. Using RIGHT JOIN instead of LEFT JOIN when Orders is the main table

Solution

1. Step 1: Identify which table's rows to keep

   If Orders is the main table and you want all its rows, LEFT JOIN should be used, not RIGHT JOIN.

2. Step 2: Understand RIGHT JOIN effect

   RIGHT JOIN keeps all rows from Customers (right table), so if Orders has rows without matching Customers, those rows are excluded.

3. Final Answer:

   Using RIGHT JOIN instead of LEFT JOIN when Orders is the main table -> Option D

4. Quick Check:

   Use LEFT JOIN to keep all left table rows [OK]

Hint: Use LEFT JOIN to keep all rows from first table [OK]

Common Mistakes:

• Confusing LEFT and RIGHT JOIN roles
• Expecting RIGHT JOIN to keep left table rows
• Ignoring join direction impact on row count

5. You have two tables: Students (left) and Enrollments (right). You want a list of all students, including those not enrolled in any course, showing NULL for missing enrollment data.
Which query is best and why?

Option A: SELECT * FROM Students LEFT JOIN Enrollments ON Students.ID = Enrollments.StudentID;
Option B: SELECT * FROM Enrollments RIGHT JOIN Students ON Students.ID = Enrollments.StudentID;

hard

A. Option A, because LEFT JOIN keeps all students and matches enrollments

B. Option B, because RIGHT JOIN keeps all enrollments and matches students

C. Option A, but it excludes students without enrollments

D. Option B, but it excludes students without enrollments

Solution

1. Step 1: Identify which table's rows to keep

   You want all students, even those without enrollments, so keep all rows from Students (left table).

2. Step 2: Choose JOIN type accordingly

   LEFT JOIN keeps all rows from Students and matches enrollments or shows NULL if none. RIGHT JOIN would keep all enrollments, not all students.

3. Final Answer:

   Option A, because LEFT JOIN keeps all students and matches enrollments -> Option A

4. Quick Check:

   LEFT JOIN keeps all left table rows [OK]

Hint: Keep main table first, use LEFT JOIN to keep all its rows [OK]

Common Mistakes:

• Using RIGHT JOIN but expecting all left table rows
• Switching table order without adjusting JOIN type
• Assuming RIGHT JOIN keeps left table rows