task LEFT JOIN · easy
Predict: members with and without bookings
Predict every member id and matched fee. Members without bookings must remain in the LEFT JOIN result.
what to return
- Columns
idfeein this order- Rows
- 5 rows · in the order asked
- Watch for
- Use the sample data shown here. NULL is not zero or empty text. Keep duplicate result rows.
- Skill
- Reason about the exact result of a fixed SQL query. Refresher: Keep unmatched rows →
expected result
Your query should return exactly these columns and values. Run it and compare.
expected result5 rows · in this order
| id | fee |
|---|---|
| 1 | 20 |
| 1 | 30 |
| 2 | NULL |
first 3 of 5 rows
data you can query
Sample rows from each table. Each column shows its type underneath; → marks a link to another table.
studio_members4 columns · 4 rows
| idinteger · key | nametext | teamtext | creditsinteger |
|---|---|---|---|
| 1 | Luz | Red | 80 |
| 2 | Kit | Red | 80 |
| 3 | Remy | Blue | 50 |
| 4 | Sol | Blue | NULL |
all 4 rows
studio_bookings4 columns · 4 rows
| idinteger · key | member_idinteger → studio_members | feeinteger | booked_attext |
|---|---|---|---|
| 11 | 1 | 20 | 2026-04-01 |
| 12 | 1 | 30 | 2026-04-30 |
| 13 | 2 | NULL | 2026-05-01 |
| 14 | NULL | 20 | 2026-04-15 |
all 4 rows
This question asks you to predict an output. The prototype covers write and debug questions; open it in the current app.
Hints and the answer are always available. Using them counts the question as solved with help.