The Morning Dashboard
You have just taken over the morning metrics review at Whetcode Supply, a small online shop, and the first slide is the one nobody argues about: how much has been sold, ever. Before any of the interesting questions get asked, the meeting wants the plainest possible figure — how many orders the shop has taken since it opened.
It is also a check on the data itself. If this number does not match what the payment provider reports, nothing further down the slide deck is worth reading.
orders — one row per order. customer_id is the id of the customer who placed it, product_id the id of the item bought, quantity how many units of that item, and order_date the day it was placed. An order row covers one item only.
| id | customer_id | product_id | quantity | order_date |
|---|---|---|---|---|
| 1 | 1 | 1 | 2 | 2023-02-01 |
| 2 | 1 | 4 | 1 | 2023-02-01 |
| 3 | 2 | 2 | 1 | 2023-02-10 |
| 4 | 3 | 3 | 3 | 2023-03-05 |
| 5 | 4 | 5 | 5 | 2023-03-11 |
| 6 | 1 | 3 | 1 | 2023-04-02 |
| 7 | 5 | 1 | 4 | 2023-05-20 |
| 8 | 2 | 5 | 2 | 2023-05-22 |
| 9 | 3 | 4 | 1 | 2023-06-01 |
| 10 | 5 | 2 | 1 | 2023-06-15 |
The table already exists in the database — there is nothing to create or load.
Task: Write a query returning one row with a single column, total_orders, holding how many rows the orders table contains. Every order counts, whatever it was for and however many units it was.
Example output — the shape, on an invented figure. A shop with forty-six orders on file would come back as:
| total_orders |
|---|
| 46 |
Sign in to solve this problem
Reading problems is free for everyone — solving them (Run, Submit, and tracking what you've solved) needs an account.
Sign in