upper.io/db VS SQLBoiler

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.

sqlboiler

My current ORM of choice is Bob [GitHub Link] which I created based on my experience using and maintaining SQLBoiler [GitHub Link].

You mean like ORMs? * sqlboiler: generates Go ORM using database schema.

SQL code generator (aka inspect a database or SQL files to generate data models). You have the option of using something like volatiletech/sqlboiler which looks at the a physical database and generates code based on the schema. Or SQLC which is an amazing and fast project.

After trying a half dozen migration engines for NodeJS, I was pleased to see Prisma and its excellent documentation. As a golang developer I am partial to SQLBoiler and its database-first approach, though perhaps this is a condition of our community where we want all the knobs. Prisma was code-first but still gave me enough control to feel confident.

I use sqlboiler which generates an ORM from your database, and sql-migrate which is a tool for managing SQL migrations. Although you have to write your migrations in SQL, which IMHO is a plus.

FWIW, the other posts point to https://gobuffalo.io/ and https://github.com/volatiletech/sqlboiler as possibilities.

My current favourite is: sqlboiler https://github.com/volatiletech/sqlboiler

I love SQL Boiler, which generates type-safe code for you from the database schema.

SQLBoiler but currently building an evolved version with generics and more flexibility.