API to obtain a GridReader given a data reader started outside Dapper
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
Sometimes we have a DbDataReader or IDataReader that could not have been obtained from Dapper, but we want to map it to types we use with Dapper all the same. Sometimes we directly obtain a SqlDataReader; other times it's a custom reader we wrote or are referencing from NuGet where there is no DbCommand or DbConnection equivalent. As far as I can tell, you can't use Dapper without starting from an (I)DbConnection.
Sometimes we also directly obtain a SqlCommand and would like to be able to use it with Dapper, so an extension method to execute a DbCommand and get back a grid reader would be awesome.
If APIs like this sound good, I'd be happy to put the work in.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review Dapper's existing GridReader and connection-based entry points, then compare the requested DbDataReader/IDataReader and DbCommand/SqlCommand paths. Define the supported API behavior and add coverage for obtaining and consuming a GridReader from each requested starting point; done means these entry points work without requiring a DbConnection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- api, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100