Re:How We Went All In on sqlc/pgx for Postgres and Go
by mrweasel on Thursday September 09, 2021 @02:38AM
(#28466958)
> Working with SQL in X (any language) usually has a poor developer experience that is why ORM or query builders are popular.
I believe that you're partly right. In my experience there's also a large number of developers who simply have no SQL training, and don't actually care to learn.
We've frequently have customers who complain about the performance of managed database (either managed by us, or a cloud provider). When we look at the queries it's clear that they use a ORM, without giving the schema it will generate much thought. It can be extremely hard to help make optimizations, because you need to figure out how to wrangle something like Hibernate into generating efficient queries and schemas, while not breaking the object model for the developers.
For my own Go projects I normally just stick to sqlx. I like that I can design the schema the way I need, and just create the queries that will map into my structs. Then it's just updates that are annoying.
I believe that you're partly right. In my experience there's also a large number of developers who simply have no SQL training, and don't actually care to learn.
We've frequently have customers who complain about the performance of managed database (either managed by us, or a cloud provider). When we look at the queries it's clear that they use a ORM, without giving the schema it will generate much thought. It can be extremely hard to help make optimizations, because you need to figure out how to wrangle something like Hibernate into generating efficient queries and schemas, while not breaking the object model for the developers.
For my own Go projects I normally just stick to sqlx. I like that I can design the schema the way I need, and just create the queries that will map into my structs. Then it's just updates that are annoying.