Closed ejball closed 3 years ago
This is a lot of extra code just for the theoretical purity of calling
DisposeAsync
.
IMHO "a lot" is overstating things a bit. It is true that this is just for completeness, operating under the assumption that they introduced IAsyncDisposable
to ADO.NET for a reason.
assumption
I don't know that that assumption is warranted in the case of DbCommand
.
This is a lot of extra code just for the theoretical purity of calling
DisposeAsync
. I'm not aware of a place that actually benefits from callingDisposeAsync
(most commands are a no-op, as are most readers if all the data has been read), so this doesn't feel worth it.