Also, SQLC doesn't allow for dynamic query building so think about an input search struct from which you may add where clauses — or not.
Also doesn't support multiple inserts with N rows being inserted.
Otherwise for standard queries, it's great.
I have a little research[1] on dynamic queries.
[1]: https://github.com/baverman/sqlbind?tab=readme-ov-file#dynam...
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.
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.
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.
If library supports named parameters they should be used by default in examples.
SQLc you write the queries, it generates the boilerplate functions to execute them.
This works better than an ORM because you don't have to deal with an ORM.
For example I have original query:
SELECT * from users where following_count > $1 and followers_count < $2;
SELECT * from users where enabled and followers_count < $1 and following_count > $2;
More likely you would introduce a new query that would get a new function call.
usersWithCountBetween(a, b)
vs
enabledUsersWithCountBetween(a,b)
If you mean, how to handle the addition of a new enabled flag that is passed in, that too would either require refactoring or a new function.
These aren't really things I would consider a problem but maybe I'm missing something?
Oh and you can configure the number of params before it replaces the params with an interface so things like this are easier to manage over time.