Why outer joins are needed in SQL - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Outer Joins

Why do we use outer joins in SQL instead of just inner joins?

A To delete rows from one table based on another table

B To speed up query execution by skipping unmatched rows

C To combine only rows that have matching values in both tables

D To include all rows from one table even if there is no matching row in the other table

💡 Hint

Think about what happens when some data in one table has no match in the other.

Outer joins allow us to keep all rows from one table and fill in NULLs for missing matches in the other table. Inner joins only keep rows with matches in both tables.

❓ query_result

intermediate

Result of LEFT OUTER JOIN

Given these tables:

Employees:
id | name
1 | Alice
2 | Bob
3 | Carol

Departments:
id | dept_name
1 | Sales
3 | HR

What is the result of this query?

SELECT Employees.name, Departments.dept_name
FROM Employees LEFT OUTER JOIN Departments ON Employees.id = Departments.id;

SQL

SELECT Employees.name, Departments.dept_name
FROM Employees LEFT OUTER JOIN Departments ON Employees.id = Departments.id;

A [('Alice', 'Sales'), ('Bob', NULL), ('Carol', 'HR')]

B [('Alice', 'Sales'), ('Carol', 'HR')]

C [('Alice', NULL), ('Bob', NULL), ('Carol', NULL)]

D [('Bob', NULL)]

💡 Hint

LEFT OUTER JOIN keeps all rows from the left table.

The LEFT OUTER JOIN returns all employees. For Bob, there is no matching department, so dept_name is NULL.

📝 Syntax

advanced

Correct Syntax for FULL OUTER JOIN

Which of the following SQL queries correctly uses FULL OUTER JOIN to combine two tables 'A' and 'B' on column 'id'?

A SELECT * FROM A JOIN FULL OUTER B ON A.id = B.id;

B SELECT * FROM A FULL OUTER JOIN B ON A.id = B.id;

C SELECT * FROM A OUTER FULL JOIN B ON A.id = B.id;

D SELECT * FROM A FULL JOIN B WHERE A.id = B.id;

💡 Hint

FULL OUTER JOIN syntax requires the keywords in a specific order.

The correct syntax is 'FULL OUTER JOIN' with ON clause specifying the join condition. Other options have wrong keyword order or missing ON.

❓ optimization

advanced

Optimizing Queries with Outer Joins

You have a large table 'Orders' and a smaller table 'Customers'. You want to list all customers and their orders, including customers with no orders. Which join and indexing strategy is best for performance?

A Use LEFT OUTER JOIN from Customers to Orders, and index Orders.customer_id

B Use INNER JOIN from Orders to Customers, and index Customers.id

C Use RIGHT OUTER JOIN from Orders to Customers, and no indexes

D Use CROSS JOIN and filter with WHERE clause

💡 Hint

Think about which table should be on the left and which column to index for fast lookups.

LEFT OUTER JOIN from Customers to Orders ensures all customers appear. Indexing Orders.customer_id speeds up matching orders lookup.

🔧 Debug

expert

Why does this OUTER JOIN query return fewer rows than expected?

Given tables:
Products(id, name)
Sales(product_id, quantity)

Query:
SELECT Products.name, Sales.quantity
FROM Products LEFT OUTER JOIN Sales ON Products.id = Sales.product_id
WHERE Sales.quantity > 10;

Why might this query return fewer rows than the total number of products?

A Because Products.id and Sales.product_id have different data types causing join failure

B Because LEFT OUTER JOIN only returns rows with matching Sales records

C Because the WHERE clause filters out rows where Sales.quantity is NULL, removing unmatched products

D Because the query syntax is invalid and causes an error

💡 Hint

Consider how WHERE conditions affect rows with NULLs from outer joins.

The WHERE clause filters after the join, so rows with no matching Sales (NULL quantity) are excluded. To keep all products, the condition should be in the JOIN or use IS NULL checks.

Practice

1. Why do we need LEFT OUTER JOIN in SQL?

easy

A. To include all rows from the left table even if there is no matching row in the right table

B. To only show rows that have matching values in both tables

C. To delete rows from the left table

D. To update rows in the right table

Solution

1. Step 1: Understand the purpose of LEFT OUTER JOIN

   LEFT OUTER JOIN returns all rows from the left table and matched rows from the right table. If no match, NULLs appear for right table columns.

2. Step 2: Compare with INNER JOIN behavior

   INNER JOIN returns only rows with matching keys in both tables, excluding unmatched rows.

3. Final Answer:

   To include all rows from the left table even if there is no matching row in the right table -> Option A

4. Quick Check:

   LEFT OUTER JOIN shows all left rows [OK]

Hint: LEFT OUTER JOIN keeps all left rows, unmatched get NULLs [OK]

Common Mistakes:

• Confusing LEFT OUTER JOIN with INNER JOIN
• Thinking it deletes or updates rows
• Assuming it only shows matched rows

2. Which of the following is the correct syntax for a LEFT OUTER JOIN?

easy

A. SELECT * FROM table1 JOIN LEFT OUTER table2 ON table1.id = table2.id;

B. SELECT * FROM table1 LEFT JOIN table2 ON table1.id = table2.id;

C. SELECT * FROM table1 OUTER LEFT JOIN table2 ON table1.id = table2.id;

D. SELECT * FROM table1 LEFT OUTER JOIN table2 WHERE table1.id = table2.id;

Solution

1. Step 1: Recall correct LEFT OUTER JOIN syntax

   The correct syntax is: SELECT ... FROM table1 LEFT JOIN table2 ON condition; LEFT JOIN is shorthand for LEFT OUTER JOIN.

2. Step 2: Identify syntax errors in other options

   SELECT * FROM table1 JOIN LEFT OUTER table2 ON table1.id = table2.id; has JOIN LEFT OUTER which is invalid order. SELECT * FROM table1 OUTER LEFT JOIN table2 ON table1.id = table2.id; uses OUTER LEFT JOIN which is incorrect. SELECT * FROM table1 LEFT OUTER JOIN table2 WHERE table1.id = table2.id; uses WHERE instead of ON for join condition.

3. Final Answer:

   SELECT * FROM table1 LEFT JOIN table2 ON table1.id = table2.id; -> Option B

4. Quick Check:

   LEFT JOIN ... ON ... is correct syntax [OK]

Hint: Use LEFT JOIN ... ON ... for correct outer join syntax [OK]

Common Mistakes:

• Swapping JOIN and LEFT keywords
• Using WHERE instead of ON for join condition
• Writing OUTER LEFT JOIN instead of LEFT OUTER JOIN

3. Given tables Employees and Departments where some employees have no department, what will this query return?

SELECT e.name, d.name FROM Employees e LEFT JOIN Departments d ON e.dept_id = d.id;

medium

A. All departments with employee names; NULL for departments without employees

B. Only employees who have a matching department

C. All employees with their department names; NULL for employees without a department

D. Only departments with employees

Solution

1. Step 1: Analyze LEFT JOIN behavior on Employees and Departments

   LEFT JOIN keeps all rows from Employees (left table). For employees without matching department, department columns show NULL.

2. Step 2: Understand output columns

   Query selects employee name and department name. Employees without department show NULL in department name.

3. Final Answer:

   All employees with their department names; NULL for employees without a department -> Option C

4. Quick Check:

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

Hint: LEFT JOIN shows all left rows, unmatched right side NULL [OK]

Common Mistakes:

• Thinking only matched rows appear
• Confusing left and right tables
• Expecting departments without employees to appear

4. What is wrong with this query if we want to list all customers and their orders, including customers with no orders?

SELECT c.name, o.order_id FROM Customers c INNER JOIN Orders o ON c.id = o.customer_id;

medium

A. INNER JOIN excludes customers without orders; should use LEFT OUTER JOIN

B. The ON clause is missing

C. The SELECT statement is missing table aliases

D. Orders table should be first in the FROM clause

Solution

1. Step 1: Understand INNER JOIN behavior

   INNER JOIN returns only rows with matching keys in both tables, so customers without orders are excluded.

2. Step 2: Identify correct join for including all customers

   LEFT OUTER JOIN keeps all customers even if no matching orders exist, showing NULL for order columns.

3. Final Answer:

   INNER JOIN excludes customers without orders; should use LEFT OUTER JOIN -> Option A

4. Quick Check:

   Use LEFT OUTER JOIN to include all left table rows [OK]

Hint: Use LEFT OUTER JOIN to include unmatched left table rows [OK]

Common Mistakes:

• Using INNER JOIN when outer join is needed
• Forgetting ON clause (though present here)
• Thinking table order in FROM matters for join type

5. You have two tables: Students and Enrollments. Some students are not enrolled in any course. Which query correctly lists all students and their courses, showing NULL for students without enrollments?

hard

A. SELECT s.name, e.course FROM Students s INNER JOIN Enrollments e ON s.id = e.student_id;

B. SELECT s.name, e.course FROM Students s RIGHT OUTER JOIN Enrollments e ON s.id = e.student_id;

C. SELECT s.name, e.course FROM Enrollments e LEFT OUTER JOIN Students s ON s.id = e.student_id;

D. SELECT s.name, e.course FROM Students s LEFT OUTER JOIN Enrollments e ON s.id = e.student_id;

Solution

1. Step 1: Identify which table has all students

   Students table contains all students, including those without enrollments.

2. Step 2: Choose join to keep all students

   LEFT OUTER JOIN with Students as left table keeps all students, adding course info or NULL if no enrollment.

3. Step 3: Evaluate other options

   INNER JOIN excludes students without enrollments. RIGHT OUTER JOIN with Enrollments left excludes students without enrollments. LEFT OUTER JOIN with Enrollments left table excludes students without enrollments.

4. Final Answer:

   SELECT s.name, e.course FROM Students s LEFT OUTER JOIN Enrollments e ON s.id = e.student_id; -> Option D

5. Quick Check:

   LEFT OUTER JOIN keeps all left table rows [OK]

Hint: LEFT OUTER JOIN with Students on left keeps all students [OK]

Common Mistakes:

• Using INNER JOIN excludes students without courses
• Swapping left and right tables in join
• Using RIGHT OUTER JOIN incorrectly