go-queryset VS upper.io/db

Looks really good and reminds me of https://github.com/jirfag/go-queryset for go/gorm.

You will be joining the expert Go team at Horizon, previously who in our spare time + for fun, authored OSS projects like chi (https://github.com/go-chi/chi), upper/db (https://github.com/upper/db), webrpc (https://github.com/webrpc/webrpc), goware (https://github.com/goware), and much more. Our Go codebases are extremely clean and the patterns we've built have been shaped over 7 years of writing production Go systems and open source projects. These are the patterns which we apply to our infrastructure at Horizon in our products Skyweaver and Sequence.

You might want to give https://upper.io/ a try

upper.io is a viable alternative to GORM. Just a suggestion.

this is the reason why I chose upper/db over pgx/sqlc for my current cockroachdb side project

while upper/db is not as type safe, with proper testing infrastructure, it's the closest to django due to its simplicity/composability/query building support

i'm also excited to see how upper/db grows after generics land in Go later this year

https://github.com/upper/db

https://upper.io/

So far, I've enjoyed using https://github.com/upper/db for raw query building.