sqlc

Yes, I was about to reply to myself with a link to this issue as I couldn't see anything in official docs unless looking at the github issues. https://github.com/kyleconroy/sqlc/issues/1157

Can you provide some resources about the lack of support for joins in sqlc? Because I wasn't able to find in official documentation and actually there's a discussion on github containing queries with join statements: https://github.com/kyleconroy/sqlc/issues/213

I stumbled across this library a few months ago and also really liked the approach. Unfortunately I had to drop it temporarily due to this issue (https://github.com/kyleconroy/sqlc/pull/983)... which I now see is solved. Taking another look. :)

This looks really cool to me, because I love to write SQL. Except for that `UPDATE` statement. That... is a problem. Looks like there is an open discussion about this on the project: https://github.com/kyleconroy/sqlc/discussions/1149

Thanks a lot for this great project. I looked in the issues for Sqlite support and saw the merge of PR to "Add three new experimental engines, including SQLite" [0] and there's major architecture changes involved. That merge was 1.5 yr ago though, and I am curious what the plans are to take that further. [0] https://github.com/kyleconroy/sqlc/pull/331

I was really really excited when I saw the title because I've been having a lot of difficulties with other Go SQL libraries, but the caveats section gives me pause. Needing to use arrays for the IN use case (see https://github.com/kyleconroy/sqlc/issues/216) and the bulk insert case feel like large divergences from what "idiomatic SQL" looks like. It means that you have to adjust how you write your queries. And that can be intimidating for new developers. The conditional insert case also just doesn't look particularly elegant and the SQL query is pretty large. sqlc also just doesn't look like it could help with very dynamic queries I need to generate - I work on a team that owns a little domain-specific search engine. The conditional approach could in theory with here, but it's not good for the query planner: https://use-the-index-luke.co

If you are into Golang, also well worth checking out sqlc. It parses your migrations to generate typed structs and query funcs https://github.com/kyleconroy/sqlc

Doing it the other way around makes more sense, i.e. write SQL to generate code. See https://github.com/kyleconroy/sqlc, why aren't more people following this approach?

I've enjoyed using https://github.com/kyleconroy/sqlc on a couple of projects. Give it your schema and queries, get type-safe interfaces in return. It's a happy medium for me between all-in ORM and raw SQL.

You might like the approach I took with pggen[1] which was inspired by sqlc[2]. You write a SQL query in regular SQL and the tool generates a type-safe Go querier struct with a method for each query. The primary benefit of pggen and sqlc is that you don't need a different query model; it's just SQL and the tools automate the mapping between database rows and Go structs. [1]: https://github.com/jschaf/pggen [2]: https://github.com/kyleconroy/sqlc

SQLC could be a good fit. It generates type-safe Go code from SQL. https://github.com/kyleconroy/sqlc

Tried sqlx a few weeks ago. I personally didn't like it. I come from a Hibernate/JVM background. Writing a data access layer with that much boilerplate isn't something I consider to be practical in today's fast paced environments. After sqlx, I gave sqlc (https://github.com/kyleconroy/sqlc) a try and I found it to be much more painless than any other database solution (for PostgreSQL) for Golang. Edit: sqlc is an inversed solution. Instead of generating SQL queries using Golang, you write annotated SQL queries and sqlc generates Golang source from them.