How We Went All In on sqlc/pgx for Postgres and Go

Re:How We Went All In on sqlc/pgx for Postgres and Go by otabdeveloper4 on Thursday September 09, 2021 @05:42AM (#28467958)

> code generation, instead of e.g. reflection

"Hey man, we noticed there's not enough compiler in your compiler, so we made a second compiler for your compiler."

[ Parent | on HN ]

Re:How We Went All In on sqlc/pgx for Postgres and Go by y4mi on Thursday September 09, 2021 @08:37AM (#28468981)

The one thing that kept annoying me with compilation type orms like this is the chicken and egg situation.

Your migrations will likely be run by your application, but your application won't compile until you've run your migrations.

[ Parent | on HN ]

Re:How We Went All In on sqlc/pgx for Postgres and Go by JulianMorrison on Thursday September 09, 2021 @06:39AM (#28468245)

"Your compiler compiles A, but you also want to compile B, so we added an extra compiler to help you compile it"

[ Parent | on HN ]

Re:How We Went All In on sqlc/pgx for Postgres and Go by Cthulhu_ on Thursday September 09, 2021 @07:36AM (#28468554)

Makes sense, Go can't compile SQL and vice versa.

[ Parent | on HN ]