Why doesn't Dapper override fields in the entity class that are defined with default values when encountering null strings in the database? about dapper

[mgravell]

Dapper's current behaviour is to skip over nulls, rather than actively assign. A case can be made for either behaviour, and I can totally get behind making this configurable - although this would most likely be over in the AOT project (see #1909 for reasons).

So: if you'd like to see a [AssignNullValues] option in Dapper.AOT: please go and log that in Dapper.AOT; it sounds pretty minimal to do there, and a nightmare to do here.