Inada Naoki

Setting `db.SetConnMaxIdleTime()` very short (e.g. ~5sec) is enough for most users. So I don't think pre-Ping option is worth enough.

> This option make Go driver re-open connections every 5 seconds for all connections in connection pool. You are talking about SetConnMaxLifetime, but I said about SetConnMaxIdleTime. > And (Not...

`readRow()` is very low level function. We intentionally avoid allocation as possible here. I know that scanning into `interface{}` has usability issue. But it is a limitation of current design...

See also: https://github.com/jmoiron/sqlx/issues/225#issuecomment-964797827

> * `go` default sql mapper is not exposed as interface where one can not override/use custom mapper. [proposal: database/sql: value converter interface for rows.Scan  golang/go#22544](https://github.com/golang/go/issues/22544) Correct. > * It...

Yes. It is intended. After `Exec()` succeeded, we don't have anything to cancel. What's wrong about it?

Could you provide a reproducible example, instead of your expectation?

For your hint, you can use `SELECT SLEEP(10)` to emulate long running query.

What is problem here? I think it is intended behavior.

I don't think your "reproducer" don't reproduce the problem you are talking. Have you really **confirmed** that "ExecContext rarely does not get an error"? Or is it just your thought?...