sqlc

What would you use if ORM is to be avoided? Perhaps something like https://github.com/sqlc-dev/sqlc ?

There are some good tips here. As for sqlc, I really wanted to like it, but it had some major limitations and minor annoyances last time I tried it a few months ago. You might want to go through its list of issues[1] before adopting it. Things like no support for dynamic queries[2], one-to-many relationships[3], embedded CTEs[4], composite types[5], etc. It might work fine if you only have simple needs, but if you ever want to do something slightly sophisticated, you'll have to fallback to the manual approach. It's partly understandable, though. It cannot realistically support every feature of every DBMS, and it's explicitly not an ORM. But I still decided to stick to the manual approach for everything, instead of wondering whether something is or isn't supported by sqlc. One tip/gotcha I recently ran into: if you run Go within containers

I missed this too. However, I've found you can work around it pretty easily with clauses like CASE WHEN @field != "" THEN column = @field ELSE true END. Example from the sqlc creator (https://github.com/sqlc-dev/sqlc/discussions/364#discussionc...): -- name: FilterFoo :many SELECT * FROM foo WHERE fk = @fk AND (CASE WHEN @is_bar::bool THEN bar = @bar ELSE TRUE END) AND (CASE WHEN @lk_bar::bool THEN bar LIKE @bar ELSE TRUE END) AND (CASE WHEN @is_baz::bool THEN baz = @baz ELSE TRUE END) AND (CASE WHEN @lk_baz::bool THEN baz LIKE @baz ELSE TRUE END) ORDER BY CASE WHEN @bar_asc::bool THEN bar END asc, CASE WHEN @bar_desc::bool THEN bar END desc, CASE WHEN @baz_asc::bool THEN baz END asc, CASE WHEN @baz_desc::bool THEN baz END desc;

I've been looking into sqlc lately for Go. Seems brilliant except for the lack of dynamic queries: https://github.com/sqlc-dev/sqlc/discussions/364

I can't find an equivalent for Go. https://github.com/sqlc-dev/sqlc and https://github.com/sqlc-dev/sqlc look nice, but they are doing codegen, definitely not as sleek as Rust sqlx. I guess it's a good example of how powerful Rust is. The "magic" that sqlx does at compile time gets really difficult if not impossible to do without macros. Of course you could create a separate parser/builder, and codegen works as well, but definitely not as convenient and flexible.

If you want to try out something cool, check out https://github.com/sqlc-dev/sqlc It's written in Go and it converts your sql migrations and queries into typesafe code that you use access your database. It currently has a plugin for Python that's in Beta, but what essentially does something similar to what this post is saying. https://github.com/sqlc-dev/sqlc-gen-python You write your migrations, and queries and a config file and it does the rest.

Some examples for anyone else reading: Go: https://github.com/kyleconroy/sqlc Rust: https://github.com/cornucopia-rs/cornucopia This is my preferred method of interacting with databases now, if available. Very flexible.

I was interested in looking up sqlc for python but it seems to be for go? Is there a different version than this? https://github.com/kyleconroy/sqlc

It's also the domain used for releases and other artifacts (after a redirect from github.com). There's going to be a lot of broken builds today: $ curl -i -L https://github.com/kyleconroy/sqlc/releases/download/v1.17.0/sqlc_1.17.0_linux_amd… HTTP/2 302 server: GitHub.com date: Fri, 24 Mar 2023 20:51:56 GMT content-type: text/html; charset=utf-8 location: https://objects.githubusercontent.com/github-production-release-asset-2e65be/19316…

Why don't you use sqlc + pgx? What's missing from the two? https://github.com/kyleconroy/sqlc https://github.com/jackc/pgx

This is pretty much the idea behind sqlc, with some extra steps of course. You write your SQL queries in file, and it generates type safe bolierplate for you. https://github.com/kyleconroy/sqlc

Would this do? https://github.com/kyleconroy/sqlc

As the post you're replying to describes, magic is antithetical to Go idioms. An ORM is basically database-as-magic, every ORM in Go is just a nightmare. Something like sqlc[0] is leagues better than any ORM in terms of simplicity, complexity and maintainability. 0: https://github.com/kyleconroy/sqlc

If you're using postgres, I'm a major fan of the anti-ORM (ROM?) that is sqlc. Nothing I've used comes in Go close in productivity or safety (and ability to write proper queries but use them very simply, and stay up-to-date without too much extra toil). Last I checked they're also working on adding sqlite support. https://github.com/kyleconroy/sqlc/