aim-database-migration

To make PostgreSQL migrations idempotent, use IF NOT EXISTS clauses in CREATE and ALTER statements. This prevents Docker Compose migrate containers from throwing already exists errors when volumes cause re-runs.

Docker Compose migrate containers fail when PostgreSQL schema files lack deterministic ordering or explicit database creation. Ensure files use NNN_description.sql naming and deploy/scripts/migrate-postgres.sh explicitly creates the database.

The best way to validate SQLC queries after changing PostgreSQL migration files is running sqlc generate followed by go test. This confirms generated models match the updated schema and queries work correctly.

Yes, you need to regenerate SQLC models every time you add a PostgreSQL migration script. Running sqlc generate after schema updates keeps generated query models consistent with the new database structure.

To enforce deterministic migration ordering for PostgreSQL schema updates, mandate NNN_description.sql filename patterns. This ensures the compose migrate init container executes scripts in correct dictionary order reliably.

No, you cannot safely use non-idempotent DDL patterns in PostgreSQL migrations managed by Docker Compose. Idempotent DDL patterns like IF NOT EXISTS are required to prevent failures when migrate containers re-run.