pgx VS sqlx

Is it better to use tools like [pgx](https://github.com/jackc/pgx) or stick with a ORM like GORM.

If your schema/migrations are not part of the go project then it might not be a great fit. It does support pgx which is a huge advantage imo vs plain database/sql.

The Wiki doesn't help to get you started?

Regarding postgres setup, it looks ok, I recommend considering pgx instead of libpq; reason being maintainability, libpq even recommends using pgx instead see README.

github.com/jackc/pgx/v4 (v4.17.1)

Is it related to https://github.com/jackc/pgx somehow?

PostgeSQL as event store database Kafka as messages broker gRPC Go implementation of gRPC Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus MongoDB MongoDB database Elasticsearch Elasticsearch client for Go. Echo web framework Kibana Kibana is data visualization dashboard software for Elasticsearch Migrate for migrations

I'd stick with this approach rather than trying to learn Gorm as well. Simple is really your friend at this point. Note that because you aren't using Gorm you will need some other way of creating your tables. The simplest way of doing this is just to execute SQL table creation DDL statements manually using `psql`. There are separate migration packages for Go, but all that can come later I think. Note also that the old `pq` driver for Postgres is in maintenance mode, so maybe look at https://github.com/jackc/pgx which seems to be the recommended way of connecting to Postgres going forward.

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.