We currently have 2 DbReader implementations, one to handle reading entities, and the other to handle reading metadata.
This works where batching isn't used and there is just a single results set for the reader to read. However when you have a bgatch of sql statements, one statement might be selecting entities and the next statement in the batch might be selecting metadata. The reader needs to provide a NextResult() method to navigate to the next result set - therefore we need a single reader that can handle both types of result sets.
We currently have 2 DbReader implementations, one to handle reading entities, and the other to handle reading metadata.
This works where batching isn't used and there is just a single results set for the reader to read. However when you have a bgatch of sql statements, one statement might be selecting entities and the next statement in the batch might be selecting metadata. The reader needs to provide a NextResult() method to navigate to the next result set - therefore we need a single reader that can handle both types of result sets.