sqlx VS go-sql-driver/mysql

sqlx

If you care about performance you might want to avoid an ORM all together and just write out the queries you need. We use sqlx in those cases.

or in general for accessing databases? * sqlx: general purpose extensions to database/sql * sqlc: generate type safe code from queries * squirrel: fluent SQL generator

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)

I understand that database/db is an abstraction. As to the driver, sorry, it completely went out of my head. The guide primarily focuses on https://github.com/go-sql-driver/mysql, which is also what I’m interested in.

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