goose VS Squirrel

In v3.16.0 we added a new Provider feature that unlocks the ability to implement a lot of highly requested features. More details in the blog post:

Next try https://github.com/pressly/goose We have this setup to be run by the CI-CD pipeline to be run before the application is started. BTW, this utility is compatible with https://sqlc.dev , so they work good together.

For database migration I recommend https://github.com/pressly/goose As it works with sqlc and is a powerful tool for complex migrations. This is something a lot of ORMs are really weak with. I was on a large project with Gorm as the ORM and what a nightmare when we pushed to production!

goose https://github.com/pressly/goose - data migration and seed data creation

I'm using .sql migration files with tooling similar to https://github.com/pressly/goose . Is there a way to manage my schema with my pre-existing tooling and my queries/CRUD operations with Ent/Atlas?

It uses Gin as the HTTP framework and PostgreSQL as the database with pgx as the driver and Squirrel as the query builder. It also utilizes Redis as the caching layer with go-redis as the client.

I would add Squirrel to PGX https://github.com/Masterminds/squirrel

I have written about this before, and my thoughts always settle on using a query builder. I've built a simple one, which works for what I need, but there are more feature complete ones out there such as squirrel. I've also written about how you can implement a simple CRUD library for database interactions using generics and query building to have that nice middle-ground between an ORM and query building.

Now for the dynamic queries you have to be really careful to prevent SQL injections, there are bunch of different ways to do it but I typically recommend using a package such as squirrel that lets you do this easily, you use it to generate the plain SQL you need (and then use sqlx, database/sql, pgx or whatever you prefer) or use it directly querying the database directly.

Here are 2 options for you * https://github.com/huandu/go-sqlbuilder * https://github.com/Masterminds/squirrel

https://www.reddit.com/r/golang/comments/vq98ud/what_sql_library_are_you_using/ Jet havn't used but is one that looks promising! Otherwise I'm one of the purests, db/sql and https://github.com/Masterminds/squirrel

I think he means an sql builder like squirrel. This allows dynamic queries, but more important you can reuse function that build a where clause so you can get a count and query with that.

I'd rather suggest the use of tools more aligned with the core concepts of the language such as sqlx, which is an extension of the database/sql standard library. It allows you to use models/structs to map your tables but you have more control over the SQL statements you use to perform queries and the like. You can combine sqlx with Squirrel to build queries from composable parts.

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.