upper.io/db VS GORM

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.

Regarding the interaction with the database, I decided to use an ORM to make the whole process simpler and more intuitive and for that reason I decided to use Gorm, which in my opinion is the most popular ORM in the Go universe and has a great range of features.

Gorm

have you used something like https://github.com/go-gorm/gorm. My guess is that i would favor sqlc because of the compile-time saftey

This article builds up on the last part where we built a simple REST API with Go. Now, let's connect our API with a real database! Here, we will use PostgreSQL and GORM to accomplish this.

Have you tried Gorm?

Short answer, you can’t, at least not directly, since sqlx isn’t an ORM. I’d check out gorm for something like that.

Do you like an ORM like eloquent for Laravel? Then I can recommend GORM https://gorm.io/

Good ORM library: https://gorm.io/

GORM

Well, if you look at Gorm's prepare_stmt.go you see that it is a thin wrapper around a database/sql.Stmt. And if you look at database/sql.Stmt you see that it's a sort of handle to an abstract entity that it creates in the database.