Migrations were run by hand and nothing recorded which had run, so re-running the setup script against an existing database failed on the first CREATE TABLE, and shipping a new migration gave an operator no way to know whether an estate had it. A missed migration is not a startup error - it is a query referencing a column that is not there, surfacing later on whichever endpoint touches it first. server/internal/migrate applies pending migrations at boot and refuses to start against a schema it does not match. One transaction per file holding both the DDL and the row that records it; an advisory lock so two servers starting at once cannot both apply 008; checksums so an edited migration is refused by name rather than silently skipped; numeric ordering so 010 does not run before 009. `migrate -baseline N` adopts a database built before any of this existed, because "the clients table exists" does not say whether 007's index does. Verified on the live database: adopted 001-007, applied 008. 008 adds two indexes on `purchases`, found by asking the database which foreign keys had nothing behind them and then checking what queries the table. The conversion report filters client_id + occurred_at, which is exactly the estate-wide case with no site to narrow it. run-local.sh had two bugs, both found by running it rather than reading it: it reused a broker container whose bind mount pointed at a directory that no longer existed, and it discarded stderr on the mosquitto_passwd call, so under `set -e` it exited at step 5 with no output at all. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HViLj9gYNRtSr7YVZmW5sn
16 lines
549 B
Go
16 lines
549 B
Go
// Package migrations carries the schema files themselves.
|
|
//
|
|
// It exists only so `go:embed` can reach them: embed cannot see outside its own
|
|
// package directory, and moving the .sql files into some internal/ folder would
|
|
// break every path that documents them - RUN.md, run-local.sh, the test that
|
|
// tells you how to build a database by hand.
|
|
package migrations
|
|
|
|
import "embed"
|
|
|
|
// FS holds every migration, named NNN_description.sql. The number is the
|
|
// version and must be unique; the rest is for humans.
|
|
//
|
|
//go:embed *.sql
|
|
var FS embed.FS
|