Why filtering behavior matters in PostgreSQL - Challenge Your Understanding

Challenge - 5 Problems

❓ query_result

intermediate

Filtering rows with WHERE vs HAVING

Consider a table sales with columns region, product, and amount. Which query correctly returns regions with total sales greater than 1000?

PostgreSQL

SELECT region, SUM(amount) AS total_sales
FROM sales
WHERE amount > 100
GROUP BY region
HAVING SUM(amount) > 1000;

A Returns regions where each individual sale is over 100 and total sales per region exceed 1000.

B Returns regions where total sales per region exceed 1000, ignoring individual sale amounts.

C Returns all regions regardless of sales amounts.

D Returns an error because WHERE cannot be used with GROUP BY.

💡 Hint

Remember that WHERE filters rows before grouping, and HAVING filters groups after aggregation.

The WHERE amount > 100 filters out sales less than or equal to 100 before grouping. Then HAVING total_sales > 1000 filters groups where the sum is greater than 1000. So only regions with individual sales over 100 and total sales over 1000 are returned.

🧠 Conceptual

intermediate

Effect of filter order on query results

Why does the order of filtering conditions matter in SQL queries involving aggregation?

A Because <code>WHERE</code> filters rows before aggregation, and <code>HAVING</code> filters after aggregation, changing the order changes results.

B Because <code>HAVING</code> always runs before <code>WHERE</code>, so order does not matter.

C Because filters in <code>WHERE</code> and <code>HAVING</code> are combined and run simultaneously.

D Because <code>WHERE</code> filters groups and <code>HAVING</code> filters individual rows.

💡 Hint

Think about when rows are filtered versus when groups are filtered.

WHERE filters rows before aggregation, so it affects which rows are included in groups. HAVING filters groups after aggregation. Changing the order changes which data is aggregated and which groups remain.

📝 Syntax

advanced

Identify the syntax error in filtering query

Which option contains a syntax error in filtering aggregated data?

PostgreSQL

SELECT department, COUNT(*) AS emp_count
FROM employees
GROUP BY department
WHERE emp_count > 10;

A The query is correct and will run without errors.

B Syntax error because GROUP BY must come after HAVING.

C Syntax error because COUNT(*) cannot be used in HAVING clause.

D Syntax error because WHERE cannot be used after GROUP BY; HAVING should be used instead.

💡 Hint

Check the order of clauses in SQL and which clause filters aggregated results.

WHERE filters rows before grouping and cannot filter aggregated results. To filter groups based on aggregate functions like COUNT, use HAVING after GROUP BY.

❓ optimization

advanced

Optimizing filtering for large datasets

Given a large orders table, which filtering approach is more efficient to find customers with more than 5 orders?

PostgreSQL

SELECT customer_id, COUNT(*) AS order_count
FROM orders
GROUP BY customer_id
HAVING COUNT(*) > 5;

A Filter rows with WHERE before grouping using COUNT(*) > 5 condition.

B Use a subquery to filter customers with more than 5 orders before grouping.

C Add an index on customer_id to speed up grouping and filtering.

D Use HAVING after GROUP BY as shown; it is efficient for large datasets.

💡 Hint

Think about how indexes affect query performance on large tables.

Indexes on columns used in GROUP BY and filtering can speed up query execution by reducing data scanned. Filtering with WHERE on aggregate functions is not possible. Using HAVING is correct but adding an index improves performance.

🔧 Debug

expert

Debugging unexpected filtering results

A query returns no rows but you expect some. The query is:

SELECT category, AVG(price) AS avg_price
FROM products
WHERE price < 200
GROUP BY category
HAVING AVG(price) > 150;

What is the most likely reason for no results?

A AVG(price) cannot be used in HAVING clause, causing no results.

B The WHERE clause filters out all rows with price ≥ 200 before grouping, so groups have fewer rows, lowering AVG(price).

C HAVING clause is filtering groups incorrectly; it should be in WHERE.

D GROUP BY category is missing, causing aggregation error.

💡 Hint

Consider how WHERE affects which rows are included before aggregation.

The WHERE clause removes all products priced 200 or more before grouping. This reduces the number of rows per category, which can lower the average price below 150, causing HAVING to filter out all groups.