N005 Tier 1 · Foundations

NULL Semantics and IS NULL in SQL

NULL represents the absence of a known value. Every NULL-related behavior in PostgreSQL follows from that single fact.

NULL is SQL's way of marking a value as missing.

In real databases, missing data is everywhere. A customer signed up but never filled in their city. An employee was just hired and doesn't have a manager yet. A session started but hasn't ended. None of those are blank strings or zeros. The data simply isn't there. SQL stores that absence as NULL.

Knowing how to handle NULL is essential for any analyst working with real data. The gaps show up constantly: incomplete customer profiles, optional fields, records that are still in-progress. When you need to find those rows, or exclude them, you use IS NULL and IS NOT NULL.

To find rows where a column has no value:

SELECT name, email
FROM customers
WHERE city IS NULL

SQL checks each row in customers. If city has no value recorded, the row passes. You get every customer with a missing city.

The inverse works the same way:

Swap IS NULL for IS NOT NULL when you want only rows that have a value — filtering out anything that's incomplete or uncategorized.

The one thing that trips people up: WHERE city = NULL never returns anything.

When SQL tries to compare a column to NULL using =, it can't produce a true or false answer. An unknown value compared to anything gives an unknown result. WHERE drops rows where the condition isn't clearly true. So = NULL fails silently, every time, for every row. IS NULL works because it doesn't try to compare. It asks a direct question: is this value absent? That always has a clear answer.

Check your understanding

A 'customers' table has a 'city' column that is sometimes NULL. Which condition returns only rows where city is missing?

Practice

9 NULL Semantics and IS NULL practice problems

These problems are part of the NULL Semantics and IS NULL lesson in SQLMaxx, with instant grading and a worked solution on each.

How you actually get good at SQL

Reading explains SQL. Writing it, over and over with instant feedback, is what makes you fluent.

That's the whole SQLMaxx loop: 600+ real problems, instant AI feedback, mastery you can actually see, and spaced review that won't let you forget.

A stack of SQL practice problem cards, the top card showing an employees table.
615 problems · 66 concepts

Real problems. Not toy examples.

615 hand-built problems spanning all 66 concepts, from basic SELECTs to window functions, built on real schemas and real business questions, the kind you'll actually get asked on the job. Enough reps to make SQL automatic.

A retro computer showing a SQL query marked correct with a green checkmark.
Instant AI feedback

Write a query. Know if it's right in one second.

No copying an answer and hoping it clicked. The AI grader checks your real query against real data, catches exactly what's wrong, and explains the fix in plain English, like a senior analyst reading over your shoulder on every problem.

A circular mastery progress dial filling from blue to green, the SQLMaxx diamond at its center.
Mastery tracking

Stop guessing whether you actually know it.

SQLMaxx tracks every concept and shows you what you've mastered and what's still shaky. Your skills fill in one concept at a time, so 'I think I get joins' becomes something you can prove.

A SQL query editor circled by a blue return arrow with a clock, scheduled to come back for review.
Spaced review

Learn it once. Keep it for good.

Most of what you learn this week fades by next week. So when a concept comes due for review, SQLMaxx hands you a fresh problem to solve from a blank editor, not a flashcard to re-read. A research-backed spaced-repetition algorithm (FSRS) times each return for right before you'd forget, so your SQL is still there months later, when the interview or the job actually needs it.

Practice, feedback, mastery, review. That's the loop that turns reading into real skill.

Start free

No account, no credit card. Start solving in under a minute.