MultiMapAsync disposes reader in unbuffered query
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
- Create unbuffered
CommandDefinitionwith flagsCommandFlags.None. - Call
QueryAsync<TFirst, ..., TReturn>(command)
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
Start at Dapper/SqlMapper.Async.cs around line 940 and reproduce the issue with an unbuffered CommandDefinition using CommandFlags.None and QueryAsync<TFirst, ..., TReturn>. Confirm the reader-disposal behavior and define done as preventing the reader from being disposed prematurely while preserving the unbuffered query behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100