Cap 217, Cap 218 and One Shared Name: The Cricket Quiz Question That Is Really a Database Stress Test

Late last week, on the Delhi night desk, a Wisden Cricket Quiz question sat open on my screen: which name do India's men's Test caps 217 and 218 share? The first reaction was the one every reader has — a list of names started running in my head. I closed the list and opened the spreadsheet. For twenty-five years I have read matches through phase splits and context rather than scorelines, and this question had no scoreline in it. What it had was a registry — Test cap numbers, incremented once per debut. The question looks like cricket. It is data classification.

I did not try to find the answer. I trust a model only after I can name the condition that would make it wrong. Here the condition is plain: the source does not supply the answer. A man who produces an answer without a source, a sample, or a stated assumption is the first red flag in someone else's copy — mine, before lunch. So this time I did not chase the answer; I chased what the question was measuring.

The Wisden quiz format is not new. Within one short item it links out to quizzes on the Sharmas in international cricket, on Test-playing Smiths, and to at least three more quiz pages. This is an engagement product, not a research product, and the gap between traffic and subscription is visible right there. The source yields thirteen information points, and not one of them is a data claim: no score, no match result, no transfer, no governance decision. That has to be stated, because converting a quiz into analysis is the easiest temptation available.

The operative rule in the quiz is not sporting but classificatory: a namesake requires an exact match. That is why four pairs are explicitly excluded — Mehidy Hasan Miraz and Mahedi Hasan, Claire Taylor and Clare Taylor, Abdul Razzaq and Abdur Razzak, Mohammad Sami and Mohammed Shami. Any reader who has at some point merged one of those four into a single player knows these names came out of a real error file, not an editor's imagination.

Test cap numbering is the only team-relevant artefact in the question. It is a BCCI and record-keeper convention: a sequential debut register, one new number per new Test player. From that a solid inference follows — caps 217 and 218 almost certainly debuted in the same Test, or in consecutive Tests. That is not the answer; it is the constraint that collapses the search space. Two adjacent caps mean the same selection meeting, the same tour, the same pitch. I am recording it as an inference, not a fact.

The real lesson sits in the bowling-type pair. Abdul Razzaq was a right-arm pace all-rounder; Abdur Razzak was a left-arm spinner — near-identical names, entirely different functions. Role and bowling type have to be stored as structured fields; that is not a nicety of cricket data, it is the floor. A model that pools those two rows corrupts its economy baseline and its matchup baseline simultaneously, and will never announce the damage.

The most consequential pair is Claire Taylor and Clare Taylor, and the reason is technical. Both are England women's internationals, so neither a team filter nor a gender filter can resolve them. What remains is spelling and date of birth. A database without spelling-level disambiguation keeps them welded together forever, two careers stacked into one record.

Zaheer Abbas is a different species of problem. His full name is Syed Zaheer Abbas Kirmani, and he chose to use his middle names — an alias created by the player, not by a database. Sharing a first and last name with his contemporary, the Indian wicketkeeper Syed Kirmani, is coincidence; the coincidence is why historical records need an alias field rather than a single name string.

The Ollie Robinson pair is where my own error bar gets tested. The one born in 2026, the Sussex pace bowler, plays Test cricket; the one born in 2026 is a wicketkeeper-batter in the English domestic game. The source claims only one has played Tests, and that claim now requires verification because such claims age quickly. I am filing it at medium confidence, not as settled fact. Mitchell Santner's joke turned on the two Daryl Mitchells — Worcestershire's captain and New Zealand's batter — and it landed because the two were broadly contemporaneous. A pair separated by decades carries no comic force.

A boundary has to be drawn here, because my trade pushes me to think in auction language. IPL auction lists and franchise shortlists are keyed on names, and a pair like Sami-Shami is a genuine mis-selection risk in a bidding room — but that is a market claim, not a cricket claim. Blending the two into one sentence is exactly the error I flag in other people's work.

Kazan did not teach me to distrust big fees; it taught me to audit small assumptions. This quiz is one of those small assumptions — that a name is an identity. The easiest move available was to guess a name and let the story run. The source withholds the answer, so any name I supplied would be an unverified assertion. In my profession that is the cheapest gain and the most expensive loss.

The most valuable part of the quiz is not the question but the exclusions. Four pairs drawn from four different cricketing ecosystems — Bangladesh, England women, Pakistan/Bangladesh, Pakistan/India — suggest a compiler working from recurring real-world confusion rather than hypotheticals. That is more useful to me than a quiz that simply answers.

One honest caveat. The existence of a quiz does not prove that namesake errors are common. It is a weak signal, and correlation is not causation: a quiz says only that a publisher believed readers would engage with it.

What genuinely worries me is that cricket's data architecture still treats the name as the primary key. Fantasy rosters, auction lists, automated scraping, archives — the name is the first field and identity is the last. Identity resolution will surface as a first-class problem within a few years, and any organisation that does not solve it now will eventually stop trusting its own records.

Next time a quiz like this appears, do not hunt the answer. Ask what your database would do with the question. The question is not what the two men are called. The question is how your system keeps them apart.