Adding typehandler based on DB side type
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
I know that there is way to add type handler based on .net class side type, however this can't be used if the dynamic is used. Is there any way to influence how the ExpandoObject is populated? Similar to json.net's converters.
Use case: I have oracle tables/queries that return RAW(16) guids in arbitrary colums. When fetched, the dynamic result will have an array of bytes instead of a guid. Which is perfectly valid, but not really usable. But only the db side type could be used to return guids as needed.
How can this be achieved?
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
The issue names no files, tests, or entry points. Start by locating Dapper’s dynamic ExpandoObject population and type-handler APIs, then determine how database-side RAW(16) values could be handled; done should be defined as a supported way to produce Guid values in dynamic results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100