Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by dhfuuvyvtt | Hacker News Reader

Parent Full thread

dhfuuvyvtt·

If you're writing a lot of dynamic queries I think you should opt for a query builder, not an orm.

For me, I write almost nothing but static queries, SQLc is just so much nicer to use.

I don't mind having to do the odd dynamic query from scratch.

I just wish sqlc supported named Params in MySQL, the resulting function param ordering is a little annoying.

View on HN

The issue with templates they could handle only simple cases or very specific complex static queries. Simple ones are a way easier with ORM/query builder. Highly depends from ORM though.

And a big NO-NO for me templates force you to repeat the same SQL in many slightly different queries. SQL composability is not a thing with templates.

Simple queries aren't any easier with ORM, that's the point of sqlc, you write the SQL and then call it as a function. There's no extra abstraction or added steps on top.

Repeating portions of sql isnt really an issue for me either, it's the business end of the database, you want it all there in one location, spreading it around in a composible fashion is just one abstraction too far. I know SQL, I don't want to learn anything else on top.

I guess you talk from only a Go perspective where you don't know any good ORM libraries. Other languages have quite convenient ORMs. Some allows even auto migrations, creating migration SQL for your.

I did a quick look at GORM. And it's a way easier and safer to use for simple cases.

Reply on news.ycombinator.com