Dapper
Dapper copied to clipboard
This PR addresses issue #1573 by modifying the GetDeserializer logic to map nullable decimal values to 0m instead of null.
- Added explicit check for
decimal?types in GetDeserializer - Returns 0m when encountering a NULL value
- Maintains existing behavior for other types
Closes #1573
Returning zero for null seems ... just wrong; unless I'm mistaken (and that does happen), we don't usually null-coalesce like this; what is the reason / scenario here?