Multi-mapping depends on order of columns
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
See this stack overflow for details on the issue.
I forked Dapper and created a small console app in the solution that illustrates the issue. Simply update the connection string as necessary (doesn't actually pull from it, just needs a valid connection to run) and then comment/uncomment the SQL statements to show the issue.
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 with the linked Stack Overflow report and the forked Dapper repository's small console app. Configure a valid connection string, run the reproduction, and compare the results while commenting and uncommenting the SQL statements. Done means multi-mapping behaves consistently regardless of column order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100