Field note · October 1, 2024

Finding the gaps in flight-delays

gaps and islands against a real schema, and the clause in it that is doing the work.

1 min read ·Analytics engineering ·sql

Finding the gaps in flight-delays comes up often enough to be worth a note. flight-delays is a convenient thing to try it on — 8,000 rows, one row per scheduled flight.

sql
with numbered as (
  select carrier, flight_date,
         row_number() over (partition by carrier order by flight_date) as rn
  from flight_delays
)
select carrier,
       min(flight_date) as island_start,
       max(flight_date) as island_end,
       count(*)   as readings
from (
  select *, date_trunc('day', flight_date) - (rn * interval '1 day') as grp_key
  from numbered
) t
group by carrier, grp_key
order by carrier, island_start;

The trick is that subtracting a dense row number from a dense date gives a constant inside a run and a different constant across a gap. Once you have seen it the query is obvious; before that it looks like a magic trick.

Run it against the real file in the SQL playground — the engine there is enough of a SQL implementation to execute this as written, and the dataset is already loaded. The pattern page has the version with the failure modes spelled out.

Window functions are the difference between SQL that describes rows and SQL that describes sequences. Almost every "we exported it to pandas to do this bit" turns out to be one of these five.