NULL behavior in comparisons in SQL - Time & Space Complexity

Time Complexity: NULL behavior in comparisons

O(n)

Understanding Time Complexity

When SQL compares values, NULL behaves differently than normal values. Understanding how this affects query time is important.

We want to know how the presence of NULLs impacts the time it takes to run comparison operations.

Scenario Under Consideration

Analyze the time complexity of the following SQL query.

SELECT *
FROM employees
WHERE salary = NULL;

-- or

SELECT *
FROM employees
WHERE salary IS NULL;
    

This code tries to find rows where the salary is NULL using two different comparison methods.

Identify Repeating Operations

Look at what happens for each row in the table.

• Primary operation: Checking the salary value for each row to see if it matches NULL.
• How many times: Once per row in the employees table.

How Execution Grows With Input

For each row, the database checks the salary column once.

Input Size (n)	Approx. Operations
10	10 checks
100	100 checks
1000	1000 checks

Pattern observation: The number of checks grows directly with the number of rows.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete the query grows in a straight line as the number of rows increases.

Common Mistake

[X] Wrong: "Using = NULL works the same as IS NULL in comparisons."

[OK] Correct: In SQL, = NULL never returns true because NULL means unknown. You must use IS NULL to check for NULL values correctly.

Interview Connect

Understanding how NULL behaves in comparisons shows you know how databases handle missing or unknown data, a key skill in writing correct queries.

Self-Check

"What if we replaced IS NULL with IS NOT NULL? How would the time complexity change?"

Practice

1. What does NULL represent in a database?

easy

A. False boolean

B. Zero value

C. Empty string

D. Missing or unknown data

Solution

1. Step 1: Understand the meaning of NULL

   NULL in databases means the data is missing or unknown, not zero or empty.

2. Step 2: Differentiate NULL from other values

   Zero, empty string, and false are actual values, while NULL means no value is stored.

3. Final Answer:

   Missing or unknown data -> Option D

4. Quick Check:

   NULL means missing or unknown data [OK]

Hint: NULL means unknown or missing, not zero or empty [OK]

Common Mistakes:

• Confusing NULL with zero
• Thinking NULL is an empty string
• Assuming NULL means false

2. Which of the following is the correct way to check if a column col is NULL in SQL?

easy

A. WHERE col = NULL

B. WHERE col == NULL

C. WHERE col IS NULL

D. WHERE col <> NULL

Solution

1. Step 1: Recall SQL syntax for NULL checks

   In SQL, to check for NULL, you must use IS NULL because = NULL does not work.

2. Step 2: Eliminate incorrect syntax

   col = NULL and col == NULL are invalid for NULL checks; col <> NULL also does not work.

3. Final Answer:

   WHERE col IS NULL -> Option C

4. Quick Check:

   Use IS NULL to check NULL values [OK]

Hint: Use IS NULL, not = or ==, to check for NULL [OK]

Common Mistakes:

• Using = NULL instead of IS NULL
• Using == NULL which is invalid in SQL
• Using <> NULL to check for NULL

3. Given a table users with a column age that contains some NULL values, what will this query return?

SELECT * FROM users WHERE age <> 30;

medium

A. All rows where age is not 30, including rows with NULL age

B. Only rows where age is not 30 and not NULL

C. Only rows where age is 30

D. No rows, because NULL causes error

Solution

1. Step 1: Understand comparison with NULL

   Comparisons like age <> 30 return UNKNOWN for NULL values, so those rows are excluded.

2. Step 2: Determine which rows are returned

   Only rows where age is not 30 and age is not NULL will be returned.

3. Final Answer:

   Only rows where age is not 30 and not NULL -> Option B

4. Quick Check:

   Comparisons with NULL exclude NULL rows [OK]

Hint: Comparisons exclude NULL rows, so NULLs are ignored [OK]

Common Mistakes:

• Assuming NULL rows are included
• Thinking NULL causes errors in comparisons
• Confusing <> with IS NOT NULL

4. You wrote this query to find rows where status is not NULL:

SELECT * FROM orders WHERE status <> NULL;

Why does it return no rows, and how to fix it?

medium

A. Comparison with NULL returns UNKNOWN; use status IS NOT NULL

B. Syntax error; use status != NULL

C. NULL is treated as zero; use status <> 0

D. Query is correct; no rows have status

Solution

1. Step 1: Understand NULL comparison behavior

   Comparing with NULL using <> returns UNKNOWN, so no rows match.

2. Step 2: Use correct syntax to check NOT NULL

   Use status IS NOT NULL to find rows where status is not NULL.

3. Final Answer:

   Comparison with NULL returns UNKNOWN; use status IS NOT NULL -> Option A

4. Quick Check:

   Use IS NOT NULL to check for non-NULL values [OK]

Hint: Use IS NOT NULL, not <> NULL, to find non-NULL rows [OK]

Common Mistakes:

• Using <> NULL instead of IS NOT NULL
• Assuming <> NULL works like != NULL
• Thinking NULL is zero or empty

5. You want to select all rows from products where discount is either NULL or greater than 10. Which query correctly returns these rows?

hard

A. SELECT * FROM products WHERE discount > 10 OR discount IS NULL;

B. SELECT * FROM products WHERE discount > 10 AND discount IS NULL;

C. SELECT * FROM products WHERE discount > 10 OR discount = NULL;

D. SELECT * FROM products WHERE discount > 10 AND discount = NULL;

Solution

1. Step 1: Understand NULL checks with OR condition

   To include NULL values, use IS NULL, not = NULL.

2. Step 2: Combine conditions correctly

   Use OR to select rows where discount is greater than 10 or discount is NULL.

3. Final Answer:

   SELECT * FROM products WHERE discount > 10 OR discount IS NULL; -> Option A

4. Quick Check:

   Use IS NULL with OR to include NULLs [OK]

Hint: Use OR with IS NULL to include NULL values in conditions [OK]

Common Mistakes:

• Using = NULL instead of IS NULL
• Using AND instead of OR with NULL checks
• Assuming NULL compares like normal values