Dapper 2.0.123 broke ExecuteImplAsync string mapping (AnsiString)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
I'm using Dapper 2.0.90, and tried to update to 2.0.123, however the update caused my code to throw.
I'm working with Snowflake DB using Snowflake.Data.Client v1.2.8, and it worked perfectly fine with Dapper v2.0.90. After the update, both QueryAsync and ExecuteAsync that contain any string parameters are failing with:
Snowflake.Data.Client.SnowflakeDbException : No corresponding Snowflake type for type AnsiString.
This means that somewhere in the changes made between .90 and .123, there is a breaking change in how strings are mapped.
Is there a chance for this to be fixed?
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
Compare Dapper 2.0.90 and 2.0.123 around the QueryAsync and ExecuteAsync parameter-mapping paths, using Snowflake.Data.Client as the reproduction context. Confirm the change that maps string parameters to AnsiString, then add coverage showing string parameters work with Snowflake without the unsupported-type exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100