Why filtering behavior matters in PostgreSQL

Introduction

Filtering helps you get only the data you need. It saves time and makes your results clear.

When you want to see only sales from last month.

When you need to find customers from a specific city.

When you want to check orders above a certain amount.

When you want to exclude canceled orders from a report.

When you want to find employees hired after a certain date.

Syntax

PostgreSQL

SELECT column1, column2 FROM table_name WHERE condition;

The WHERE clause is used to filter rows based on a condition.

Only rows that meet the condition will be shown in the result.

Examples

Shows all orders where the amount is greater than 100.

PostgreSQL

SELECT * FROM orders WHERE amount > 100;

Shows names and cities of customers who live in New York.

PostgreSQL

SELECT name, city FROM customers WHERE city = 'New York';

Shows employees hired on or after January 1, 2023.

PostgreSQL

SELECT * FROM employees WHERE hire_date >= '2023-01-01';

Sample Program

This creates a products table, adds three products, and then selects only those with a price greater than 2.00.

PostgreSQL

CREATE TABLE products (id SERIAL PRIMARY KEY, name TEXT, price NUMERIC);
INSERT INTO products (name, price) VALUES
('Pen', 1.20),
('Notebook', 2.50),
('Backpack', 25.00);

SELECT name, price FROM products WHERE price > 2.00;

Important Notes

Filtering reduces the amount of data you work with, making queries faster.

Be careful with conditions to avoid missing important data.

Filtering happens after data is selected from the table but before results are shown.

Summary

Filtering helps you focus on the data you want.

Use the WHERE clause to set conditions.

Filtering makes your queries faster and results clearer.

Practice

1. What is the main purpose of the WHERE clause in a PostgreSQL query?

easy

A. To create a new table

B. To sort the results alphabetically

C. To join two tables together

D. To filter rows based on a condition

Solution

1. Step 1: Understand the role of WHERE clause

   The WHERE clause is used to specify conditions that rows must meet to be included in the result.

2. Step 2: Compare options with WHERE purpose

   Sorting is done by ORDER BY, joining by JOIN, and creating tables by CREATE TABLE, so these are incorrect.

3. Final Answer:

   To filter rows based on a condition -> Option D

4. Quick Check:

   WHERE filters rows = A [OK]

Hint: WHERE filters rows to get only what you want [OK]

Common Mistakes:

• Confusing WHERE with ORDER BY
• Thinking WHERE creates tables
• Mixing WHERE with JOIN

2. Which of the following is the correct syntax to filter rows where the column age is greater than 30?

easy

A. SELECT * FROM users FILTER age > 30;

B. SELECT * FROM users WHERE age > 30;

C. SELECT * FROM users HAVING age > 30;

D. SELECT * FROM users ORDER BY age > 30;

Solution

1. Step 1: Identify correct filtering syntax

   The WHERE clause is used to filter rows based on conditions like age > 30.

2. Step 2: Eliminate incorrect clauses

   FILTER is not valid here, HAVING is for groups, ORDER BY sorts results, so only WHERE is correct.

3. Final Answer:

   SELECT * FROM users WHERE age > 30; -> Option B

4. Quick Check:

   WHERE filters rows correctly = A [OK]

Hint: Use WHERE for row conditions, HAVING for groups [OK]

Common Mistakes:

• Using HAVING without GROUP BY
• Using FILTER instead of WHERE
• Confusing ORDER BY with filtering

3. Given the table employees with columns id, name, and salary, what will this query return?

SELECT name FROM employees WHERE salary >= 50000;

medium

A. All employee names with salary equal or greater than 50000

B. Syntax error due to missing GROUP BY

C. All employee names regardless of salary

D. All employee names with salary less than 50000

Solution

1. Step 1: Analyze the WHERE condition

   The condition salary >= 50000 filters employees with salary 50000 or more.

2. Step 2: Understand SELECT output

   Only the name column is selected for those filtered employees.

3. Final Answer:

   All employee names with salary equal or greater than 50000 -> Option A

4. Quick Check:

   WHERE salary >= 50000 filters names = D [OK]

Hint: WHERE filters rows; SELECT chooses columns [OK]

Common Mistakes:

• Thinking it returns all employees
• Confusing >= with <
• Expecting GROUP BY needed here

4. Identify the error in this query:

SELECT * FROM orders WHERE status = 'shipped' AND;

medium

A. Incorrect use of WHERE instead of HAVING

B. Missing ORDER BY clause

C. Missing condition after AND

D. Using * instead of column names

Solution

1. Step 1: Check WHERE clause syntax

   The WHERE clause ends with AND but no condition follows, causing syntax error.

2. Step 2: Validate other parts

   HAVING is not needed here, ORDER BY is optional, and * is valid to select all columns.

3. Final Answer:

   Missing condition after AND -> Option C

4. Quick Check:

   AND must be followed by condition = B [OK]

Hint: AND must always have a condition after it [OK]

Common Mistakes:

• Leaving AND without condition
• Confusing WHERE and HAVING
• Thinking ORDER BY is mandatory

5. You want to find customers who placed orders with total amount over 100 but only if their account is active. Which query correctly filters this?

SELECT customer_id FROM orders WHERE total > 100 AND account_status = 'active';

hard

A. This query correctly filters customers with total > 100 and active accounts

B. The query should use HAVING instead of WHERE for filtering

C. The query needs GROUP BY customer_id to filter correctly

D. Filtering on account_status is invalid in WHERE clause

Solution

1. Step 1: Understand filtering conditions

   Both conditions total > 100 and account_status = 'active' filter rows correctly in WHERE clause.

2. Step 2: Check if GROUP BY or HAVING needed

   Since no aggregation is used, GROUP BY or HAVING is not required here.

3. Final Answer:

   This query correctly filters customers with total > 100 and active accounts -> Option A

4. Quick Check:

   WHERE filters multiple conditions correctly = C [OK]

Hint: Use WHERE for multiple conditions without aggregation [OK]

Common Mistakes:

• Using HAVING without aggregation
• Adding unnecessary GROUP BY
• Thinking account_status can't be filtered in WHERE