pgx VS go-sql-driver/mysql

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.

Authentication method mismatch is not allowed to occur more than once. It is not a part of MySQL protocol. go-sql-driver also has the same rule.

go-sql-driver/mysql 12.1k Stars, Used by 72.4k

> mysql_real_escape_string is still vulnerable when being used with some exotic character sets

Indeed -- mysql_real_escape_string "mostly" fixes this problem by requiring a connection as one of its args, and since it's usually aware of the connection state, it can check that to see if one of those exotic charsets is in-use. But the problem is that there are multiple ways to change the connection charset, some of which the driver is aware of (e.g. in PHP mysqli set_charset) but some it is not (running textual statements like SET NAMES or SET CHARACTER SET).

But generally an attacker won't ever have the ability to set an arbitrary exotic character set for the connection, unless they already have some other sql injection mechanism, in which case it's a moot point :)

Driver documentation also typically mentions this problem. For example, here's the doc for doing client-side param interpolation in the most popular MySQL driver for Golang: https://github.com/go-sql-driver/mysql#interpolateparams

It also explicitly detects if your initial connection settings attempt to use one of those charsets along with param interpolation, and throws an error if so: https://github.com/go-sql-driver/mysql/blob/21f789cd/dsn.go#...

> Couldn't one just save the extra round-trip with length-prefixed strings by sending the query together with the parameters in a single message?

AFAIK, no, not with the traditional MySQL binary protocol. The newer "X protocol" introduced in MySQL 5.7 does allow this, but it is not widely implemented in drivers.

However, you can use something like this https://github.com/go-reform/reform to help you with, I will call it automating the code writing. But I have always opted to one of the supported drivers and written a queries myself using for example this https://github.com/go-sql-driver/mysql.

For DB connection, you'll need something like https://github.com/Go-SQL-Driver/MySQL/ for mysql

I'm following Alex Edwards web dev book, he uses MySQL with go-sql-driver/mysql , i want to use Postgres, which one should I use?

go-sql-driver/mysql is the main pure golang implementation and is the most feature complete. Very happy with the result that it provides.

https://github.com/go-sql-driver/mysql/issues/561 , and it's not coming anytime soon

Missing support: - Go go-sql-driver/mysql - PHP

Go MySQL driver Link