Bradley Grainger

DbDataSource (https://github.com/dotnet/runtime/issues/64812) could allow the `ILoggerFactory` to be specified.

Now supported in [Connector/NET 8.0.28](https://dev.mysql.com/doc/relnotes/connector-net/en/news-8-0-28.html) through `Password1`, `Password2`, `Password3` connection string options.

It would be less convenient than connection string options, but could the `ProvidePasswordCallback` be leveraged to provide MFA passwords?

It seems like this should work; I've created #179 to investigate it. In my current PR, the connection is reset synchronously when `MySqlConnection.Dispose` is called; since the caller is still...

Another benefit of resetting the connection (in the background) as soon as it's returned to the pool is that it would immediately free up any session-specific server variables (e.g., temp...

> What about adapting Close and CloseAsync to reset the session if they are called by the user. Dispose would still not reset the connection. This would give high latency...

Alternatively, we could follow npgsql's approach and prepend the "connection reset" packet to the first query that's sent on a connection retrieved from the pool; see npgsql/npgsql#552.

> #179 was closed in favor of #264, but the later was also closed :( Those were both implementations that weren't viable. This issue remains open to track the problem....

One benefit of the current approach is that resetting the connection (on retrieval from the pool) checks the liveness of the connection. (An idle connection can be closed by the...

> What do you think about letting the user configure how they want to handle it? If the current behaviour were changed, it would probably be exposed as an opt-in...