One Contact per Email
Medium About 20 min Katabench Pro
Keep one canonical row per duplicate group with ROW_NUMBER over a priority ordering, not GROUP BY aggregates.
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
- Top N per group
- Pick the latest or best rows per group, with explicit tie handling and deduplication.
- Window functions
- LAG, LEAD, running sums and shares computed over partitions without collapsing rows.
Related katas
- Top N per Group with a Window Function Hard Pro Use ROW_NUMBER() OVER (PARTITION BY ...) to rank within groups and take the top few.
- Every Order at the Latest Instant Medium Pro Find each customer's latest order timestamp without throwing away other orders tied at that same instant.
- The Second Purchase Is Per Customer Medium Pro Use a correlated bounded subquery to select each customer's second chronological order.
- Risk Bands That Do Not Split Ties Medium Pro Assign percentile risk bands with CUME_DIST so accounts with equal scores remain together.