Filter Rows Matching a List of Values with IN
Return the payments made by credit card or debit card.
The challenge runs on the SQLabHub practice database (SQLite) and uses the payments table. You can solve it in the browser, with nothing to install.
The task
Find payments made by credit card or debit card.
A correct answer returns 42 rows with 8 columns: id, order_id, user_id, amount, method, status, paid_at, transaction_id.
Tables used in this challenge
payments 200 rows
id INTEGER (PK) · order_id INTEGER · user_id INTEGER · amount REAL · method TEXT · status TEXT · paid_at TEXT · transaction_id TEXT
| id | order_id | user_id | amount | method | status | paid_at | transaction_id |
|---|---|---|---|---|---|---|---|
The first rows of each table are shown. See how all the tables relate on the database schema page.
Expected output
| id | order_id | user_id | amount | method | status | paid_at | transaction_id |
|---|---|---|---|---|---|---|---|
First 5 of 42 rows. This is the output of the model solution on the practice database. The task does not fix a sort order, so your rows may come back in a different order.
What you practise
- Returning every column of a table with SELECT *
- Filtering rows with a WHERE condition
- Matching a column against a list of values with IN
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
Use IN with both card methods
Show the step-by-step approach
How the model solution is built, in the order the database evaluates it:
- Read from the
paymentstable. - Filter in
WHERE: keep the rows wheremethodis one of 'Credit Card' or 'Debit Card'. - Return every column with
SELECT *.
Model solution
Checking your session…
What to watch for
IN ('Credit Card', 'Debit Card') is shorthand for two equality tests joined by OR, and it stays readable as the list grows. The values must match the stored text exactly, capitals and space included: 'credit card' finds nothing.
- IN. NOT IN returns no rows at all if the list contains a NULL. With literal lists that is easy to avoid; with a subquery it is a common trap.
- WHERE. WHERE is evaluated before the SELECT list, so it cannot use a column alias defined there or the result of an aggregate.
- SELECT *. SELECT * is fine for exploring, but its output changes whenever a column is added to the table. Queries that feed a report should name their columns.
Related SQL challenges
- Filter Rows Where a Column Equals a Text ValueSimilar levelEasy
- Filter Rows on a Boolean Flag ColumnSimilar levelEasy
- Find Orders That Took More Than 3 Days to ShipHarderMedium
- Filter Rows After a Given DateSimilar levelEasy
- Compare Two Columns in a WHERE ClauseSimilar levelEasy
Keep learning
- Lesson: WHERE IN
- Lesson: WHERE Clause
- Lesson: The BIG 6 SQL Clauses
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database