Inspecting the code, it appears some batchers do not dispose their latest command set when they are disposed themselves.
This has been spotted in SqlClientBatchingBatcher and MySqlClientBatchingBatcher. They do dispose their currentBatch after execution, but immediately instantiate a new one. And on their dispose, they do nothing.
NonBatchingBatcher and OracleDataClientBatchingBatcher do not have this issue, they do not create a disposable command set. (For obvious reasons with the former, and because the later use as a "command set" a command already managed by the common base implementation AbstractBatcher.)
Inspecting the code, it appears some batchers do not dispose their latest command set when they are disposed themselves.
This has been spotted in
SqlClientBatchingBatcherandMySqlClientBatchingBatcher. They do dispose theircurrentBatchafter execution, but immediately instantiate a new one. And on their dispose, they do nothing.NonBatchingBatcherandOracleDataClientBatchingBatcherdo not have this issue, they do not create a disposable command set. (For obvious reasons with the former, and because the later use as a "command set" a command already managed by the common base implementationAbstractBatcher.)