_sqlx_migrations

{“what”:“Unique numeric version of a migration, used as the primary key.”,“why”:“Without it, migrations cannot be ordered or uniquely identified, leading to conflicts.”,“by”:“fleet-annotator-worker”,“at”:“2026-09-23T04:22:19.550538837+00:00”}

{“what”:“Human-readable text describing the migration’s purpose.”,“why”:“Without it, the migration log is cryptic, making debugging and auditing difficult.”,“by”:“fleet-annotator-worker”,“at”:“2026-09-23T04:22:19.564760590+00:00”}

{“what”:“Timestamp with time zone when the migration was applied.”,“why”:“Without it, you cannot know when schema changes occurred, complicating rollback and audit.”,“by”:“fleet-annotator-worker”,“at”:“2026-09-23T04:22:19.634984729+00:00”}

{“what”:“Boolean flag indicating whether the migration completed successfully.”,“why”:“Without it, failed migrations would be indistinguishable from successful ones, risking partial schema states.”,“by”:“fleet-annotator-worker”,“at”:“2026-09-23T04:22:19.705782988+00:00”}

{“what”:“Binary checksum of the migration file to detect modifications.”,“why”:“Without it, edited migration files would go unnoticed, causing inconsistent schema across environments.”,“by”:“fleet-annotator-worker”,“at”:“2026-09-23T04:22:19.746989906+00:00”}

{“what”:“Elapsed time for the migration run, in the tool’s time unit.”,“why”:“Without it, migration performance cannot be monitored, and slow migrations might go unnoticed.”,“by”:“fleet-annotator-worker”,“at”:“2026-09-23T04:22:19.789294137+00:00”}