SQL: NOT IN with a NULL in the subquery returns no rows at all

NOT IN expands to a chain of <> comparisons. One NULL makes every comparison UNKNOWN, and UNKNOWN is not TRUE, so the whole predicate fails for every row - an empty result set from a query that looks obviously correct.

• SQL: a stale row estimate is why the planner chose the wrong join
• SQL: READ COMMITTED lets the same query return different rows twice
• SQL: consistent lock ordering is the only cure for deadlocks
• SQL: SELECT DISTINCT is usually a join fan-out you have not fixed
• SQL: COUNT(column) is not COUNT(*), and neither is COUNT(DISTINCT)
• SQL: OFFSET pagination gets slower the deeper the user goes

---

Run this yourself in the Online Java Compiler, spin up a live REST API in the API Sandbox, or practise with Java interview questions.

Published 2026-08-25

© Java Coding Hub · About · Contact · Privacy · Terms