Match Rows with JOIN
Part of the Connected Data section of Coddy's PostgreSQL journey. Lesson 1 of 25.
An order stores a customer id instead of repeating customer details. JOIN ... ON matches rows using a relationship. Short table aliases such as c and o make qualified column names easier to read.
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 o.id, c.name FROM orders AS o JOIN customers AS c ON c.id = o.customer_id ORDER BY o.id;Order 11 matches customer 1, Ari. Ari appears again for order 12 because one customer can have several orders. A join returns matching pairs, not one row per customer.
Join related keys with ON and qualify ambiguous column names with a table alias.
Challenge
MediumReturn order_id and city for every order with a matching customer. Order by order_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