db-generation-hygiene

To keep sqlc generated bindings in sync with database migrations, run the generation command after editing SQL files and commit both the SQL sources and the generated Go output together to prevent drift.

Drift between sqlc queries and generated server bindings occurs when SQL source files in migrations or queries directories are updated without regenerating the bindings and committing the corresponding Go output.

To apply new SQL migrations and update sqlc bindings correctly, create your migration file, run the generation command from the repo root, verify the diffs under the generated directory, and commit all changes together.

Yes, you need to commit generated sqlc Go files alongside SQL queries. Committing both the source SQL files and the generated output together maintains consistency and ensures review and CI workflows reflect actual schema changes.

You need to regenerate sqlc server bindings whenever you edit SQL query files, update the sqlc configuration file, or create new migration files to ensure the generated Go code accurately reflects the current database schema.