What line_no actually contains in retail-orders

Working through retail-orders again. line_no is the column people trip over, so here is what it actually looks like.

7,000 rows, no nulls, 4 distinct values. Line number inside the order.

The five-number version: min 1, p10 1, median 1, p90 3, max 4. The mean is 2.

The p10 to p90 band — 1 to 3 — is where ordinary rows live, and it is the pair worth quoting when somebody asks what to expect. Min and max describe the two strangest rows in the table and nothing else; they are useful for spotting impossible values and misleading for everything else.

select
  count(*)                  as rows,
  count(line_no)            as present,
  count(*) - count(line_no) as nulls,
  count(distinct line_no)   as distinct_values
from retail_orders;

The mean sits 58% above the median, which is the whole story: anything that reports the average of line_no is reporting a number most rows are below. Put the median next to it or drop the mean.

Where this bites: a filter like line_no > 2 reads as "above average" and selects a minority of rows — a smaller minority than the phrase suggests to whoever asked for it. If the request was "the typical ones", the threshold they meant was 1.

The grain is one row per order line, which is the context every one of those numbers depends on. None of them survive a change of grain, which is why "profile the column" and "profile the table" are the same job. Full schema, and the CSV, on the dataset page.