DapperLib / DapperLib/Dapper.Contrib
Insert truncates all insert ids to integer size, but then converts it to a long on return: may I help fix it?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 293
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Description
The Insert method returns a long, but internally it converts the dynamic to an integer and then to a long, thus it doesn't actually support a long id. I would like to help fix this if that would be acceptable. I want to make sure that there is a pathway to get changes merged, as I notice that there haven't been any commits in 4 years. I'm happy to do the work and help revive this project, as well as fix other bugs. Please feel free to reach out to me or comment here if it would be acceptable.
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 locating the Insert method and trace its dynamic-to-integer conversion. Verify with a long identifier that the returned long preserves the inserted ID, then confirm the change through the project's tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100