You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dapper's pipelining works by executing up to 100 MySqlCommand objects "simultaneously" (using ExecuteNonQueryAsync), then recycling the commands once they complete.
This appears to be a breaking change when switching from MySql.Data to MySqlConnector because the async operations actually complete synchronously, making it just a synchronous loop.
As per DapperLib/Dapper#1469 (comment), I'd say that Dapper's pipelining is not supported, and recommend using MySqlBatch instead.
Dapper supports a "pipelining" feature: https://riptutorial.com/dapper/example/18/performing-operations-against-multiple-sets-of-input
A user reports an exception when trying to use it with MySqlConnector: DapperLib/Dapper#1469
Is this something that should be expected to work, or is it not actually supported by the MySQL protocol?
The text was updated successfully, but these errors were encountered: