bqb VS SQLBoiler

But using a query builder, something like squirrel or (plug) bqb, allows you to actually write SQL (or something close to it) when you need it but also handles the nasty string building bits. Though I agree that ORMs are not always bad, especially for small projects with well-defined scope.

Plug for bqb as a query builder, but there's also squirrel which works pretty well too.

(plug) bqb for very simple query building.

Squirrel is great! Let me also plug bqb.

Plug: BQB (basic query builder) is small, 100% test coverage, and in AwesomeGo. A great starter project.

I totally understand this. If you do go with a query builder, may I recommend bqb (shameless plug) as it allows you to remain closer to the SQL than some alternatives and doesn't do anything fancy. We stripped out 50% of our query logic with it in our org, which has enabled us to more readily tweak the SQL for performance.

There's also bqb. We use it in production at our company -- much better than raw SQL. If you couple it with something like scany then you get more of the ORM benefits without the complexity.

Another shameless plug: https://github.com/nullism/bqb pretty tiny query builder with 100% test coverage

SQLBoiler takes a database-first approach, generating Go code from your database schema. This means it creates highly optimized and custom-tailored code for your specific database schema. SQLBoiler is great for applications where the database schema is well-defined and changes infrequently. However, like sqlc, it requires regenerating the code when the database schema changes. It's well-suited for projects where performance is a key concern and the database design is stable​.

Moved all my projects to https://github.com/volatiletech/sqlboiler.

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.