Why subqueries are needed in PostgreSQL - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Subqueries in SQL

Why do we use subqueries in SQL? Choose the best explanation.

A To create multiple tables at once in a single SQL statement.

B To perform a query inside another query to filter or calculate data before the main query runs.

C To speed up the database server by running queries in parallel automatically.

D To permanently store query results as new tables without writing extra commands.

💡 Hint

Think about how subqueries help break down complex questions into smaller parts.

Subqueries let you run a query inside another query. This helps you filter or calculate data first, then use that result in the main query. It makes complex data retrieval easier and clearer.

❓ query_result

intermediate

Output of a Subquery Filtering

Given the tables employees (id, name, department_id) and departments (id, name), what is the output of this query?

SELECT name FROM employees WHERE department_id IN (SELECT id FROM departments WHERE name = 'Sales');

PostgreSQL

employees:
1, 'Alice', 2
2, 'Bob', 3
3, 'Charlie', 2
4, 'Diana', 1
departments:
1, 'HR'
2, 'Sales'
3, 'Marketing'

A Alice, Bob, Charlie

B Bob, Diana

C Alice, Charlie

D Diana

💡 Hint

Look at which department has the name 'Sales' and match employees with that department_id.

The subquery finds the id of the 'Sales' department, which is 2. The main query selects employees whose department_id is 2. That includes Alice and Charlie.

📝 Syntax

advanced

Identify the Syntax Error in Subquery Usage

Which option contains a syntax error in using a subquery in PostgreSQL?

PostgreSQL

SELECT * FROM orders WHERE customer_id = (SELECT id FROM customers WHERE name = 'John');

A SELECT * FROM orders WHERE customer_id = (SELECT id FROM customers WHERE name = 'John' LIMIT 1);

B SELECT * FROM orders WHERE customer_id = (SELECT id FROM customers WHERE name = 'John');

C SELECT * FROM orders WHERE customer_id = ANY (SELECT id FROM customers WHERE name = 'John');

D SELECT * FROM orders WHERE customer_id IN SELECT id FROM customers WHERE name = 'John';

💡 Hint

Check the placement of parentheses and keywords around the subquery.

Option D is missing parentheses around the subquery after IN, which causes a syntax error. The correct syntax requires parentheses enclosing the subquery.

❓ optimization

advanced

Why Use Subqueries Instead of Joins in Some Cases?

Which reason best explains why a subquery might be preferred over a JOIN in a query?

A Subqueries can simplify queries when filtering based on aggregated results that are hard to express with JOINs.

B Subqueries always run faster than JOINs because they use less memory.

C Subqueries automatically create indexes to speed up queries, unlike JOINs.

D Subqueries allow combining data from unrelated tables without any conditions.

💡 Hint

Think about when you need to filter by a calculated value like a maximum or count.

Subqueries are useful when you want to filter rows based on aggregated data, such as maximum values or counts, which can be complex to do with JOINs alone.

🔧 Debug

expert

Debugging a Subquery Returning Multiple Rows Error

What error will this query produce and why?

SELECT name FROM employees WHERE department_id = (SELECT id FROM departments WHERE location = 'New York');

Assume the subquery returns multiple department ids.

A ERROR: subquery returns more than one row because '=' expects a single value.

B No error, query runs successfully returning all matching employees.

C ERROR: syntax error near '=' because subqueries cannot be used in WHERE clauses.

D ERROR: missing FROM clause in subquery.

💡 Hint

Consider what happens when a subquery returns more than one value but '=' expects one.

The '=' operator expects a single value on the right side. If the subquery returns multiple rows, PostgreSQL raises an error about multiple rows returned.

Practice

1. Why do we use subqueries in PostgreSQL?
SELECT * FROM employees WHERE department_id IN (SELECT id FROM departments WHERE location = 'NY');

easy

A. To change data types of columns

B. To speed up the database server automatically

C. To ask a question inside another query and filter results based on it

D. To create new tables from existing ones

Solution

1. Step 1: Understand the role of the subquery

   The subquery (SELECT id FROM departments WHERE location = 'NY') finds department IDs located in NY.

2. Step 2: See how the main query uses the subquery

   The main query selects employees whose department_id matches any ID from the subquery result.

3. Final Answer:

   To ask a question inside another query and filter results based on it -> Option C

4. Quick Check:

   Subqueries filter data using inner query results [OK]

Hint: Subqueries answer inner questions to filter outer query [OK]

Common Mistakes:

• Thinking subqueries speed up queries automatically
• Confusing subqueries with table creation
• Using subqueries to change data types

2. Which of the following is the correct syntax for a subquery in PostgreSQL?

easy

A. SELECT * FROM table WHERE column == (SELECT MAX(column) FROM table);

B. SELECT * FROM table WHERE column = (SELECT MAX(column) FROM table);

C. SELECT * FROM table WHERE column = SELECT MAX(column) FROM table;

D. SELECT * FROM table WHERE column IN SELECT MAX(column) FROM table;

Solution

1. Step 1: Identify correct subquery syntax

   Subqueries must be enclosed in parentheses and used with comparison operators like = or IN.

2. Step 2: Check each option

   SELECT * FROM table WHERE column = (SELECT MAX(column) FROM table); correctly uses parentheses and = with a subquery. The other options have syntax errors like using == instead of =, omitting parentheses entirely, or missing them after IN.

3. Final Answer:

   SELECT * FROM table WHERE column = (SELECT MAX(column) FROM table); -> Option B

4. Quick Check:

   Subqueries need parentheses and proper operators [OK]

Hint: Subqueries always go inside parentheses [OK]

Common Mistakes:

• Using double equals (==) instead of single equals (=)
• Omitting parentheses around subqueries
• Using IN without parentheses

3. What will be the output of this query?

SELECT name FROM employees WHERE salary > (SELECT AVG(salary) FROM employees);

medium

A. Syntax error due to subquery

B. Names of employees earning less than the average salary

C. All employee names

D. Names of employees earning more than the average salary

Solution

1. Step 1: Understand the subquery

   The subquery (SELECT AVG(salary) FROM employees) calculates the average salary of all employees.

2. Step 2: Apply the condition in the main query

   The main query selects employee names where their salary is greater than this average.

3. Final Answer:

   Names of employees earning more than the average salary -> Option D

4. Quick Check:

   Subquery returns average; main query filters salaries above it [OK]

Hint: Subqueries can return single values to compare in main query [OK]

Common Mistakes:

• Thinking it returns employees below average
• Assuming syntax error due to subquery
• Confusing AVG with SUM

4. Identify the error in this query:

SELECT name FROM employees WHERE department_id = SELECT id FROM departments WHERE name = 'Sales';

medium

A. Missing parentheses around the subquery

B. Wrong comparison operator used

C. Subquery returns multiple rows causing error

D. Incorrect table name used

Solution

1. Step 1: Check subquery syntax

   The subquery must be enclosed in parentheses to be valid in the WHERE clause.

2. Step 2: Identify the missing parentheses

   The query misses parentheses around SELECT id FROM departments WHERE name = 'Sales', causing syntax error.

3. Final Answer:

   Missing parentheses around the subquery -> Option A

4. Quick Check:

   Subqueries need parentheses to be valid [OK]

Hint: Always put subqueries inside parentheses [OK]

Common Mistakes:

• Forgetting parentheses around subqueries
• Assuming wrong operator causes error
• Thinking table name is incorrect

5. You want to find employees who earn more than the average salary in their own department. Which query correctly uses a subquery to achieve this?

hard

A. SELECT name, salary, department_id FROM employees WHERE salary > (SELECT AVG(salary) FROM employees WHERE department_id = employees.department_id);

B. SELECT name, salary FROM employees WHERE salary > (SELECT AVG(salary) FROM employees);

C. SELECT name FROM employees WHERE salary > ALL (SELECT salary FROM employees);

D. SELECT name FROM employees WHERE salary > ANY (SELECT AVG(salary) FROM employees GROUP BY department_id);

Solution

1. Step 1: Understand the requirement

   We need to compare each employee's salary to the average salary of their own department.

2. Step 2: Analyze each option

   SELECT name, salary, department_id FROM employees WHERE salary > (SELECT AVG(salary) FROM employees WHERE department_id = employees.department_id); uses a correlated subquery that calculates average salary per employee's department. SELECT name, salary FROM employees WHERE salary > (SELECT AVG(salary) FROM employees); compares to overall average, ignoring departments. SELECT name FROM employees WHERE salary > ALL (SELECT salary FROM employees); compares salary to all salaries, not averages. SELECT name FROM employees WHERE salary > ANY (SELECT AVG(salary) FROM employees GROUP BY department_id); compares to a list of averages but uses ANY incorrectly.

3. Final Answer:

   SELECT name, salary, department_id FROM employees WHERE salary > (SELECT AVG(salary) FROM employees WHERE department_id = employees.department_id); -> Option A

4. Quick Check:

   Correlated subquery compares salary to department average [OK]

Hint: Use correlated subqueries to compare within groups [OK]

Common Mistakes:

• Comparing to overall average instead of department average
• Using ALL or ANY incorrectly with averages
• Not correlating subquery with outer query