go-pg VS SQLBoiler

I usually work with PostgreSQL and have used https://github.com/go-pg/pg. https://github.com/uptrace/bun is its successor.

bun and go-pg both seem to work fairly well for these kind of purposes.

gorm.io/gorm`, or `github.com/go-pg/pg` if you need something more feature-rich. I would avoid using `go-kit` and `go-micro` "frameworks" unless you have some special requirement for it. But you can take a look to have an idea of what Go "framework" may look like.

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.

SQLBoiler it's fast and generates type-safe compile-able code.

Take a look at sqlboiler. It's an ORM that generates the database models for you based on the SQL schema.

I like sqlboiler. Generate a Go ORM based on your DB schema.