HardSQL challenge #356WINDOW FUNCTIONRUNNING AVERAGEANALYTICS

Cumulative Density Orders

Find cumulative average order value over time.

The challenge runs on the SQLabHub practice database (SQLite) and uses the orders table. You can solve it in the browser, with nothing to install.

Solve This SQL Challenge

The task

Find cumulative average order value over time.

A correct answer returns 200 rows with 2 columns: order_date, cum_avg.

Tables used in this challenge

orders 200 rows

id INTEGER (PK) · user_id INTEGER · total REAL · discount REAL · item_count INTEGER · status TEXT · order_date TEXT · shipped_date TEXT · shipping_city TEXT · shipping_country TEXT

First 3 rows of the orders table
iduser_idtotaldiscountitem_countstatusorder_dateshipped_dateshipping_cityshipping_country
1432638.110.253cancelled2024-04-24NULLLos AngelesUSA
2829470.195delivered2024-03-152023-04-09ChicagoUSA
3136683.240.082delivered2023-02-152023-07-10Los AngelesUSA

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
order_datecum_avg
2022-01-061843.49
2022-01-102881.965
2022-01-152305.3533333333335
2022-01-162576.93
2022-01-172894.298

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

  • Accumulating a value row by row with an ordered window

Hint and approach

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

Show the hint

AVG OVER

Show the step-by-step approach

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

  1. Read from the orders table.
  2. Compute AVG(total) as a running window function: it covers the rows from the start up to the current one, ordered by order_date.

Model solution

Checking your session…

What to watch for

  • Running totals. With ORDER BY and no frame, rows that tie on the sort column are added together in one step. Use ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW for a strict row-by-row total.
Solve This SQL Challenge

Keep learning