go-pg VS sqlx

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.

https://github.com/jmoiron/sqlx and github.com/lib/pq are pretty solid, this is what i go to.

The amount of packages imported is kind of a thing I want to remove. There is, for example, MySQL package but I use PG. Also, for many things I need sqlx, sometimes database/sql + carta. I would love to standardize all my database handling to make it simple, concise, and efficient;

Implement the Repository interface by writing the queries in code, perhaps using some solution like Squirrel or sqlx.

Hey, have you looked at sqlx?

sqlx: sqlx is a library which provides a set of extensions on go's standard database/sql library. (https://github.com/jmoiron/sqlx)

sqlx for database connections. It allows scanning into structs which saves a lot of time and is easier to use.

I typically use sqlx to deal with query results.

Beyond that, as others have suggested, sqlx is very close to dapper in terms of functionality. It’s not generic, but generics don’t actually get you anything here except dapper will instantiate the types for you while with sqlx you have to do it yourself. Under the hood, both must use reflection to map fields.

You could try https://github.com/jmoiron/sqlx. Not sure it will satisfy your usecase to the point, but it is easy to work with wrapper of database/sql and provides some nice mappings. Take a look at https://jmoiron.github.io/sqlx/ for some more advanced use cases than just githubs README.

If it is to low-level for your liking maybe take a look at sqlx or even gorm.