It groups rows that have the same values in specified columns into summary rows, like finding the total sales per product.
Click to reveal answer
beginner
How do you use GROUP BY with a single column?
You list one column after GROUP BY to group rows by that column's values. For example, GROUP BY department groups all rows by each department.
Click to reveal answer
intermediate
How does GROUP BY work with multiple columns?
You list multiple columns separated by commas after GROUP BY. This groups rows by unique combinations of those columns. For example, GROUP BY city, department groups rows by each city and department pair.
Click to reveal answer
beginner
Why do you often use aggregate functions with GROUP BY?
Because GROUP BY creates groups, aggregate functions like SUM(), COUNT(), or AVG() calculate summary values for each group.
Click to reveal answer
intermediate
What happens if you select columns not in the GROUP BY clause or aggregate functions?
PostgreSQL will give an error because every selected column must be either grouped or aggregated to avoid confusion about which row's value to show.
Click to reveal answer
What does GROUP BY department do?
AGroups rows by each unique department
BSorts rows by department
CDeletes duplicate departments
DFilters rows with department
✗ Incorrect
GROUP BY department groups rows that share the same department value into one group.
Which query groups by both city and department?
AGROUP BY city; GROUP BY department
BGROUP BY city OR department
CGROUP BY city, department
DGROUP BY city AND department
✗ Incorrect
Use commas to list multiple columns in GROUP BY, like GROUP BY city, department.
Which aggregate function counts rows in each group?
ACOUNT()
BMAX()
CAVG()
DSUM()
✗ Incorrect
COUNT() counts the number of rows in each group.
What error occurs if you select a column not in GROUP BY or aggregated?
ASyntax error
BColumn must appear in the GROUP BY clause or be used in an aggregate function
CMissing FROM clause
DNo error
✗ Incorrect
PostgreSQL requires all selected columns to be grouped or aggregated to avoid ambiguity.
What is the result of GROUP BY?
AA single row
BRows deleted
CRows sorted alphabetically
DRows grouped into summary rows
✗ Incorrect
GROUP BY groups rows into summary rows based on column values.
Explain how to use GROUP BY with one and multiple columns in PostgreSQL.
Think about grouping by one column versus grouping by pairs or more.
You got /4 concepts.
Why must columns in SELECT be either in GROUP BY or aggregated?
Consider what happens if you select a column not grouped or aggregated.
You got /4 concepts.
Practice
(1/5)
1. What does the GROUP BY clause do in a PostgreSQL query?
easy
A. It updates values in the specified columns.
B. It sorts the rows in ascending order.
C. It deletes duplicate rows from the table.
D. It groups rows that have the same values in specified columns.
Solution
Step 1: Understand the purpose of GROUP BY
The GROUP BY clause collects rows that share the same value in one or more columns into groups.
Step 2: Differentiate from other clauses
Unlike ORDER BY which sorts rows, GROUP BY organizes rows into groups for aggregation.
Final Answer:
It groups rows that have the same values in specified columns. -> Option D
Quick Check:
GROUP BY = groups rows by column values [OK]
Hint: GROUP BY collects rows sharing column values into groups [OK]
Common Mistakes:
Confusing GROUP BY with ORDER BY
Thinking GROUP BY deletes duplicates
Assuming GROUP BY updates data
2. Which of the following is the correct syntax to group data by two columns, category and region?
easy
A. SELECT category, region, COUNT(*) FROM sales GROUP BY category, region;
B. SELECT category, region, COUNT(*) FROM sales GROUP BY category region;
C. SELECT category, region, COUNT(*) FROM sales GROUP BY (category, region);
D. SELECT category, region, COUNT(*) FROM sales GROUP category, region;
Solution
Step 1: Check correct GROUP BY syntax
In PostgreSQL, multiple columns are separated by commas in GROUP BY without parentheses.
Step 2: Validate each option
SELECT category, region, COUNT(*) FROM sales GROUP BY category, region; uses commas correctly; SELECT category, region, COUNT(*) FROM sales GROUP BY category region; misses comma; SELECT category, region, COUNT(*) FROM sales GROUP BY (category, region); uses parentheses incorrectly; SELECT category, region, COUNT(*) FROM sales GROUP category, region; misses BY keyword.
Final Answer:
SELECT category, region, COUNT(*) FROM sales GROUP BY category, region; -> Option A
Quick Check:
GROUP BY columns separated by commas [OK]
Hint: Separate multiple columns with commas in GROUP BY [OK]
Common Mistakes:
Omitting commas between columns
Using parentheses around columns
Forgetting the BY keyword
3. Given the table orders with columns customer_id, product_id, and quantity, what will this query return?
SELECT customer_id, SUM(quantity) FROM orders GROUP BY customer_id;
medium
A. Total quantity ordered by each customer.
B. Total quantity ordered by each product.
C. Total quantity ordered by each customer and product.
D. Syntax error due to missing GROUP BY columns.
Solution
Step 1: Analyze the SELECT and GROUP BY columns
The query groups rows by customer_id and sums quantity for each group.
Step 2: Understand the aggregation result
SUM(quantity) calculates total quantity per customer_id, ignoring product_id.
Final Answer:
Total quantity ordered by each customer. -> Option A
Quick Check:
GROUP BY customer_id sums quantity per customer [OK]
Hint: GROUP BY column matches SELECT non-aggregates [OK]
Common Mistakes:
Assuming product_id affects grouping
Thinking query returns per product totals
Confusing aggregation with filtering
4. Identify the error in this query:
SELECT product_id, region, COUNT(*) FROM sales GROUP BY product_id;
medium
A. COUNT(*) cannot be used with GROUP BY.
B. Missing region in GROUP BY causes error.
C. product_id cannot be grouped alone.
D. Syntax error due to missing FROM clause.
Solution
Step 1: Check SELECT columns vs GROUP BY columns
SELECT includes product_id and region, but GROUP BY only has product_id.
Step 2: Understand PostgreSQL grouping rules
All non-aggregated columns in SELECT must appear in GROUP BY; region is missing.
Final Answer:
Missing region in GROUP BY causes error. -> Option B
Quick Check:
All SELECT non-aggregates must be in GROUP BY [OK]
Hint: Include all non-aggregated SELECT columns in GROUP BY [OK]
Common Mistakes:
Forgetting to add all columns to GROUP BY
Thinking COUNT(*) disallows grouping
Ignoring SELECT and GROUP BY mismatch
5. You want to find the total sales quantity for each product in each region from the sales table with columns product_id, region, and quantity. Which query correctly groups and sums the data?
hard
A. SELECT product_id, SUM(quantity) FROM sales GROUP BY product_id;
B. SELECT product_id, region, SUM(quantity) FROM sales GROUP BY product_id;
C. SELECT product_id, region, SUM(quantity) FROM sales GROUP BY product_id, region;
D. SELECT product_id, region, SUM(quantity) FROM sales;
Solution
Step 1: Identify grouping needs
We want totals per product and per region, so both columns must be grouped.
Step 2: Check each option's GROUP BY clause
SELECT product_id, region, SUM(quantity) FROM sales GROUP BY product_id, region; groups by product_id and region, matching SELECT columns; others miss region or GROUP BY entirely.
Final Answer:
SELECT product_id, region, SUM(quantity) FROM sales GROUP BY product_id, region; -> Option C
Quick Check:
Group by all non-aggregated columns for correct totals [OK]
Hint: Group by all selected non-aggregated columns [OK]
Common Mistakes:
Grouping by only one column when selecting multiple
Omitting GROUP BY causing aggregation errors
Selecting columns without aggregation or grouping
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.