Skip to content

Avoid passing DBNull to scalar type handlers - #2253

Open
alaricd wants to merge 1 commit into
DapperLib:mainfrom
pengdows:fix/issue-224
Open

alaricd wants to merge 1 commit into
DapperLib:mainfrom
pengdows:fix/issue-224

Conversation

@alaricd

@alaricd alaricd commented Oct 24, 2026

Copy link
Copy Markdown

Fixes #224.

Nullable scalar queries should return null for a DBNull result instead of passing DBNull into a custom type handler. Adds a fakeDb regression test that verifies the handler is not invoked for the null value.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Non-nullable TypeHandler passed DBNull when selecting scalar results

1 participant