EasySQL challenge #94WHERE

Successful Payments

Find payments with status success.

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.

Solve This SQL Challenge

The task

Find payments with status success.

A correct answer returns 137 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

First 3 rows of the payments table
id	order_id	user_id	amount	method	status	paid_at	transaction_id
1	46	105	921.62	Gift Card	success	2022-05-18	TXNHTN4GIK5L
2	157	37	1723.82	Bank Transfer	success	2024-11-11	TXNKJPIXJOFP
3	45	36	978.76	Bank Transfer	refunded	2023-10-24	TXNU2RW4MK1R

The first rows of each table are shown. See how all the tables relate on the database schema page.

Expected output

Expected output of the challenge
id	order_id	user_id	amount	method	status	paid_at	transaction_id
1	46	105	921.62	Gift Card	success	2022-05-18	TXNHTN4GIK5L
2	157	37	1723.82	Bank Transfer	success	2024-11-11	TXNKJPIXJOFP
5	18	57	538.06	Debit Card	success	2022-02-22	TXN2HY68WN6E
7	149	106	1953.21	Apple Pay	success	2024-08-28	TXN3E12GFTY7
8	94	109	182.62	PayPal	success	2024-06-01	TXNB5J4S1SN1

First 5 of 137 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

Hint and approach

Try the challenge first. Open these only when you need them.

Show the hint

Filter status

Show the step-by-step approach

How the model solution is built, in the order the database evaluates it:

Read from the payments table.
Filter in WHERE: keep the rows where status equals 'success'.
Return every column with SELECT *.

Model solution

Checking your session…

What to watch for

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.