splitOn can't handle NULL value
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
Hi,
I noticed splitOn can't handle NULL value. for example: if I use sth like select c.*, c1.* from ..., when xxx_id is the first column of table c1 and its value is null, dapper will fail to convert it into the mapping type, instead return a null.
My work around is manual inserting a id field like select c.*, 1 as id, c1.* from ....
and dapper works well.
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
No files or tests are named. Start by reproducing the reported splitOn mapping with a c., c1. query where the first c1 key is NULL, then trace the splitOn entry point. Done means the NULL related value maps correctly without requiring an injected id column, with regression coverage for that case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100