Co-authored-by: NJohn Doe <john@doe>

* Update Readme.md

* Added additional braces

* Update Readme.md

* fix #1945

* PR number

* docs

* Adds MatchConstructorParametersWithUnderscores option

* generalize to single MatchNamesWithUnderscores (pre-existing)

* cite 2nd PR

---------
Co-authored-by: NJonas Goronczy <goronczy.jonas@gmail.com>

I'll do a pass at all of these later, but getting CVE versions out of the pipe.

Resolving 4 alerts here: https://github.com/DapperLib/Dapper/security/dependabot

* if we stop supporting DbDataReader, someone is going to complain; I'd
rather wrap it for now (to make the lib work), and add an analyzer
in AOT that shouts at them for using IDbConnection

also: compiler nits

* release notes

It works fine with MySqlConnector 1.1.0

* impl QueryUnbufferedAsync<T>
* implement GridReader.ReadUnbufferedAsync<T>

We want to use latest SDK and ability to run against net6.0 tests. It looks like the pool issue with VS 2022 has been resolved on the AppVeyor side so: yay! That solves everything cleanly with no installs.

add support for fetching values via GetFieldValue<T>; this requires
DbDataReader, but in reality the reader is *always* DbDataReader;
acknowledge this, and stop pretending to use IDataReader internally
(no breaks to public API)

I just paraphrased the summaries from the sub-packages' Nuget Readmes and added them to the grid of packages in the Readme. Is that a good spot for them, and are those summaries sufficient? PR would close #1488 

Co-authored-by: NNick Craver <nrcraver@gmail.com>

As per https://docs.microsoft.com/en-us/dotnet/core/tools/sdk-errors/netsdk1174 `-p` is deprecated in favor of `--project`
This PR fixes the deprecation warning when running the benchmarks as currently described in the README.

Considering all of the inquiries on StackOverflow about DynamicParameters, there should probably be a simple overview in the documentation.
Examples:

- https://stackoverflow.com/questions/12723922/dapper-adddynamicparams-for-in-statement-with-dynamic-parameter-name
- https://stackoverflow.com/questions/43412455/dapper-with-sql-query-dynamic-parameters
- https://stackoverflow.com/questions/38443739/passing-dynamically-created-sql-parameters-into-dapper-as-an-anonymous-type
- https://stackoverflow.com/questions/62448900/how-do-i-loop-through-dapper-dynamic-query-results-using-strings-as-parameters
- https://stackoverflow.com/questions/36735189/dapper-dynamicparameters-returning-error

* snowflake tests #1687

* actually add the tests!

* merge

* context: #1716 https://github.com/DapperLib/Dapper/issues/1716

- change type-map to allow nullable
- change DateTime/TimeSpan to null
- do not specify DbType for null
- semi-breaking change: swap GetDbType to SetDbType, noting that it is marked [Obsolete] and internal-use-only
- semi-breaking change: make LookupDbType return nullable (same internal-use/[Obsolete])

* add test for Npgsql 6.0.0-rc.1

* try list parameters (like arrays)

* never assign -1 (sentinel) as the .DbType

* postgres tests

Fix verbiage for return type documentation comments.

Another example for "Execute a command Multiple Times" when we have an existing collection. The existing example (which still remains) I found to be a little bit confusing when I had an existing collection. So hopefully this 2nd example will help a tiny bit.

* snowflake tests #1687

* actually add the tests!