Find Missing Matches
Part of the Connected Data section of Coddy's PostgreSQL journey. Lesson 4 of 25.
A left join can find records without a related row. After joining, test a right-side key with IS NULL. Test a key known to be present on real matches, not an optional attribute.
Input table customers:
id | name | city |
|---|---|---|
1 | Ari | Haifa |
2 | Bo | Haifa |
3 | Cleo | Eilat |
4 | Dee | Eilat |
Input table orders:
id | customer_id | amount | ordered_on | status | meta |
|---|---|---|---|---|---|
11 | 1 | 20 | 2025-01-02 | paid | {"channel":"web","items":2,"shipping":{"city":"Haifa"}} |
12 | 1 | 30 | 2025-01-04 | paid | {"channel":"app","items":3,"shipping":{"city":"Haifa"}} |
13 | 2 | 30 | 2025-02-01 | pending | {"channel":"web","items":1} |
14 | 3 | 50 | 2025-02-03 | paid | {"channel":"app","items":5,"shipping":{"city":"Eilat"}} |
15 | 2 | 10 | 2025-02-03 | paid | {"channel":"web","items":2} |
SELECT c.id, c.name FROM customers AS c LEFT JOIN orders AS o ON o.customer_id = c.id AND o.status = 'pending' WHERE o.id IS NULL ORDER BY c.id;Ari, Cleo and Dee have no pending order. A customer with paid orders can still satisfy this query because the ON condition looks only for pending matches.
LEFT JOIN followed by a null test on a right-side key finds missing matches.
Challenge
MediumReturn id and name for customers who have never placed any order. Order by id.
The input tables are shown in the test panel. Each run starts from fresh data. Return the named columns in the stated order; do not hard-code the displayed rows.
Try it yourself
-- Write your SQL here.
This lesson includes a short quiz. Start the lesson to answer it and track your progress.
All lessons in Connected Data
1Connect Tables
Match Rows with JOINKeep Rows with LEFT JOINCount After a JoinFind Missing MatchesCustomer CoveragePractice on your own: PostgreSQL playground