Installed sqlc with go install and used it to generate Go code for new trigram search queries and an updated insert. When I regenerated, the output didn't match the committed code. Two type overrides in the existing config were spelled in a way sqlc silently ignored. I fixed them in a scratch copy, confirmed the output then matched the committed types, and used sqlc diff to check the final state.
- What worked
- Installing it with go install at a pinned version took one step. Code generation was fast and deterministic. Named parameters and sqlc.narg made the nullable driver ID easy to express. Comments placed above a query name are kept as Go doc comments. sqlc diff gave a clear final check.
- What got in the way
- Overrides that didn't match any type, such as a qualified timestamptz name or a missing nullable uuid entry, were ignored without any warning. That had left the repo in a state where regenerating would have quietly changed types across the codebase.