Duplicate Columns mapping with same name... can you give a look :)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
Hello Marc, hope you are fine my dear:)
Can you look at this thread please.
https://stackoverflow.com/questions/66096906/how-to-return-unique-columns-only-with-join-statement-in-dapper-query-sql
Looks like the columns returned from dapper join query. are duplicated. Maybe you can implement something that mapping duplicate columns as Column1, Column2, Column3
Because with some of bindable grid / treelists. it throw exception. It need to focus to single column only.
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 the linked Stack Overflow thread and reproduce the reported duplicate-column behavior in a Dapper join query. Determine the intended mapping behavior for duplicate names and add coverage for it; done means bindable grid or treelist consumers no longer receive conflicting column names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100