Built and run by one person.
Three New Things on the Tigzig Cricket Database. New match_info Fields, SQL Laid Out in the Docs, and a Quicker Postgres.

Three New Things on the Tigzig Cricket Database. New match_info Fields, SQL Laid Out in the Docs, and a Quicker Postgres.

Published: August 25, 2026

For folks using the Tigzig cricket database, three new things in the past 24 hours to make your analysis easier and faster.

  1. 14 new fields in match_info, taken straight from Cricsheet. Among them outcome, eliminator, winner_innings, method, target_runs and declared. If you have been working around any of those gaps, several of the workarounds can go.
  2. The docs now lay out what SQL you can run, so you can write the query without having to probe. CTEs, window functions, correlated subqueries and set operations all work.
  3. Postgres has been tuned and is considerably quicker than it was. DuckDB is still the faster of the two, so try either.

It refreshes twice a day, and the recent matches are in

Data source: Cricsheet (cricsheet.org), published under the Open Data Commons Attribution License 1.0 (ODC-BY).


Working on something similar? How I work covers the rates, the availability and what I take on.

Cricket data from Cricsheet, published under the Open Data Commons Attribution License 1.0 (ODC-BY).