DapperLib / DapperLib/Dapper

IEnumerable<string> does not respect TypeMap

Open
#200 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:typehandlers needs-info
Dominant language
C#
Stars
18.4k
Forks
3.7k
Avg merge
5h 8m
Merged PRs (30d)
1

Description

Setting the typemap to map string to AnsiString works with a single parameter. When passing in an IEnumerable it automatically uses String instead of looking up the DBType in the typemap.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The payload names no files or tests. Start by tracing how Dapper binds a single string parameter versus an IEnumerable and where TypeMap or DBType is consulted; compare both paths and add a regression test showing that the enumerable case respects the configured AnsiString mapping.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend-api-design, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.