The Running Total That Jumped
Medium About 25 min Katabench Pro
A running balance over tied timestamps prints the same end-of-batch total on every line of the batch, because the default window frame folds rows that tie into one.
The full brief is part of Katabench Pro
Pro opens this kata's brief, its starter code and its grader. To see how the track works first, try Customer Order Totals, which is free.
How it is graded
Your LINQ or SQL runs against real PostgreSQL. You see the SQL your code generates on the sample tests and can inspect its execution plan, so you learn when the database did the wrong work.
What it practices
- Window frames
- ROWS, RANGE and GROUPS frames, peers and exclusions, so moving windows mean what they say.
- Window functions
- LAG, LEAD, running sums and shares computed over partitions without collapsing rows.
- Deterministic ordering
- Make ORDER BY total with tie-breakers so limits, pages and aggregates stay stable.
Related katas
- Three Price Tiers of Depth Medium Pro Use a GROUPS window frame to measure rolling auction depth across distinct price tiers without splitting peers.
- The Last Event Is Not This Event Medium Pro Annotate every session event with its true final event by giving LAST_VALUE the full partition frame.
- Compare It to Everyone but Itself Medium Pro Build a centered peer average with an explicit window exclusion so the current transaction cannot hide its own anomaly.
- Choose the Auction Clearing Price Hard Pro Build cumulative demand and supply at every active limit price, then choose a clearing price with deterministic volume, imbalance, and reference-price priorities.