Marc Gravell

Yup; there are a few moving parts here - not much, but more than I wanted to rush and screw up, hence he omission. Consider me suitably poked.

The difficulty I have with this is: what is the behavior with the wide range of ADO.NET providers that _aren't SQL Server_; for example, does it work on Oracle? It...

My limited understanding (from [here](https://learn.microsoft.com/en-us/sql/connect/ado-net/configurable-retry-logic-sqlclient-introduction) is that `.RetryLogicProvider` can be specified at the connection level; so *for that*: no changes would be required. At the *command* level: no, this is...

Honestly, today is the first time I've heard of it. Typically, we prefer to target the primary ADO.NET API surface (since we don't want to force any provider-specific dependency trees),...

I agree with @billrob's comments above; additionally, a low effort implementation is probably more harmful than helpful. If we you transient retry and resilience - that sounds like a job...

Yes, the type-handler API is limited and applied inconsistently; if we make a change here, it will be [over in the AOT project](https://github.com/DapperLib/Dapper/issues/1909), but what I'm thinking is something along...

It was never not clear. My point is: yes, we know it is limited right now, and *my plan* is to focus all feature additions at the AOT model, which...

Add `commandType: CommandType.StoredProcedure)` to the Execute. I have been toying with adding this automatically if it isn't specified and the SQL does not contain any whitespace characters. I cannot think...

Also `parameters.GetValue(name)` - I've also been toying with a simpler API for this!

Ah, right. I didn't notice the `OracleDynamicParameters` - I assumed you were using Dapper. That type is not something that Dapper provides, so: for guidance on that you'd need to...