CASE in WHERE clause in SQL - Time & Space Complexity
We want to understand how using a CASE statement inside a WHERE clause affects the time it takes to run a query.
Specifically, how does the query's work grow when the data gets bigger?
Analyze the time complexity of the following SQL query.
SELECT *
FROM orders
WHERE
(CASE
WHEN status = 'shipped' THEN CASE WHEN delivery_date < CURRENT_DATE THEN 1 ELSE 0 END
ELSE CASE WHEN customer_id = 123 THEN 1 ELSE 0 END
END) = 1;
This query selects orders based on a condition that changes depending on the order status.
Look for repeated work done by the query.
- Primary operation: Checking each row in the orders table against the CASE condition.
- How many times: Once for every row in the table.
As the number of rows grows, the database checks the CASE condition for each row.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | 10 checks |
| 100 | 100 checks |
| 1000 | 1000 checks |
Pattern observation: The work grows directly with the number of rows.
Time Complexity: O(n)
This means the query takes longer in a straight line as the table gets bigger.
[X] Wrong: "Using CASE in WHERE makes the query run slower than a simple condition because it's more complex."
[OK] Correct: The database still checks each row once; the CASE just changes the condition logic but does not add extra loops.
Understanding how conditional logic inside queries affects performance helps you write clear and efficient database code.
What if we replaced the CASE with multiple OR conditions? How would that change the time complexity?
Practice
CASE in a WHERE clause allow you to do in SQL?Solution
Step 1: Understand the role of CASE in WHERE
The CASE expression in WHERE lets you choose which condition to apply depending on data values in each row.Step 2: Compare with other options
Creating new columns is done with SELECT, sorting with ORDER BY, and joining with JOIN, not CASE in WHERE.Final Answer:
Apply different filter conditions based on row values -> Option CQuick Check:
CASE in WHERE = conditional filtering [OK]
- Thinking CASE creates new columns
- Confusing CASE with ORDER BY
- Assuming CASE controls JOIN logic
CASE inside a WHERE clause?Solution
Step 1: Review correct CASE syntax
The correct CASE syntax uses WHEN condition THEN result ELSE result END. WHERE CASE WHEN age > 18 THEN 'adult' ELSE 'minor' END = 'adult' follows this exactly.Step 2: Identify syntax errors in other options
Options B, C, and D misuse CASE syntax by missing WHEN or ELSE keywords or incorrect placement.Final Answer:
WHERE CASE WHEN age > 18 THEN 'adult' ELSE 'minor' END = 'adult' -> Option BQuick Check:
CASE WHEN ... THEN ... ELSE ... END [OK]
- Omitting WHEN keyword
- Using CASE without END
- Placing conditions incorrectly
Employees with column salary, what rows will this query return?SELECT * FROM Employees WHERE CASE WHEN salary >= 50000 THEN 1 ELSE 0 END = 1;
Solution
Step 1: Understand the CASE condition
The CASE returns 1 if salary is 50000 or more, else 0.Step 2: Apply the WHERE filter
The WHERE clause keeps rows where CASE result equals 1, so salary must be at least 50000.Final Answer:
Rows where salary is 50000 or more -> Option DQuick Check:
salary >= 50000 = filtered rows [OK]
- Thinking it returns rows below 50000
- Confusing equality with greater than
- Ignoring ELSE result
SELECT * FROM Orders WHERE CASE order_status WHEN 'shipped' THEN TRUE ELSE FALSE;
Solution
Step 1: Check CASE syntax completeness
The CASE expression must end with END keyword, which is missing here.Step 2: Verify other parts
TRUE/FALSE usage is valid, CASE can be used in WHERE, and THEN keyword is present.Final Answer:
Missing END keyword for CASE expression -> Option AQuick Check:
CASE ... END required [OK]
- Forgetting END keyword
- Thinking CASE can't be in WHERE
- Misplacing THEN keyword
Products so that if category is 'Electronics', only products with stock > 0 are shown; otherwise, show products with price < 100. Which WHERE clause using CASE is correct?Solution
Step 1: Understand CASE returns boolean condition
The CASE must return TRUE or FALSE to filter rows properly.Step 2: Check syntax and comparison
WHERE CASE WHEN category = 'Electronics' THEN stock > 0 ELSE price < 100 END = TRUE correctly uses WHEN condition THEN boolean expression ELSE boolean expression END = TRUE to filter rows.Step 3: Identify why others are wrong
Options A, B, and D miss the END keyword for the CASE expression, causing syntax errors.Final Answer:
WHERE CASE WHEN category = 'Electronics' THEN stock > 0 ELSE price < 100 END = TRUE -> Option AQuick Check:
CASE returns boolean, compare with TRUE in WHERE [OK]
- Missing END keyword
- Using CASE with simple WHEN without condition
- Returning non-boolean values in CASE
Ready to prove it?
Pass the test and this pattern moves unknown
