Bradley Grainger

It looks like this is the module that was referenced: https://github.com/mithrandyr/SimplySql.

It's intended that `lock (m_lock)` (in `VerifyConnected`) should be very quick; however, I suppose if there were contention and the lightweight .NET CAS locking mechanism got promoted to a full...

> this issue also happens on single-threaded benchmarks where we open a single session Are you able to share this benchmark code?

> we do periodically get a spike of errors accessing the database with the following error How frequently do these spikes occur? Is it every 10 minutes, when `UsePeriodicPasswordProvider` calls...

> When executing CommandBehaviour.SchemaOnly on insert/update statements, it executes the command in the backend which is not the desired behaviour for this command. What should it do instead? ---- `CommandBehavior.SchemaOnly`...

> Shouldn't it be functioning in the same way how it is working SQL. In SQL CommandBehaviour.SchemaOnly works for select, insert, update as well. MySQL Server is a different database...

Normally I'd say this sounds like it's probably more related to your client OS or .NET version than MySqlConnector. However, I would expect that to consistently fail. If it only...

> But why the initial attempt with TLS 1.3 fails, I don't yet know. ... What could be the cause of the failed negotiation (i.e. the initial issue)? Did you...

I'd like to eliminate steps 3-5 above: https://github.com/mysql-net/MySqlConnector/issues/1409 However, that won't fix the failure in step 2. My general advice is to add retry support (e.g., with Polly); networks and...

> I'm happy to test again when https://github.com/mysql-net/MySqlConnector/issues/1409 is resolved. That's now fixed in [2.3.4](https://github.com/mysql-net/MySqlConnector/releases/tag/2.3.4).