Files
zeekay 266fac2a55 a migration that reads a column depends on the one that adds it
`insights_externaldatasource` is shaped by two chains: `data_warehouse` added
`access_method` in its `0026`, and `warehouse_sources` adopted the model with that field
already declared. Nothing orders the two apps against each other, so on a fresh install
this backfill ran while `data_warehouse` was still at `0009`, and died at

    column insights_externaldatasource.access_method does not exist

Every database that already ran this had the column by then, which is why only a fresh
build sees it.

Naming the migration that adds the column is the ordering. It goes here rather than on the
`warehouse_sources` move, which would be the tidier home but cycles: `data_warehouse.0020`
reads `warehouse_sources.ExternalDataSource` from state, so that chain already depends on
the move.
2026-08-09 07:41:34 -07:00
..
…