DapperLib / DapperLib/Dapper.Contrib
explicit key caching issue after update
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 293
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Description
Hey Guys,
This has been fixed a while ago for non-async:
But never made it here:
Same applies for delete.
Best!
Rob
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 by comparing Dapper.Contrib/SqlMapperExtensions.Async.cs around line 201 with the linked non-async implementation and its referenced commit. Trace the async update and delete paths to understand where explicit-key caching differs; done means those paths match the established non-async behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100