Dapper.NET Handling Nulls null vs DBNull
Example
In ADO.NET, correctly handling null is a constant source of confusion. The key point in dapper is that you don't have to; it deals with it all internally.
- parameter values that are
nullare correctly sent asDBNull.Value - values read that are
nullare presented asnull, or (in the case of mapping to a known type) simply ignored (leaving their type-based default)
It just works:
string name = null;
int id = 123;
connection.Execute("update Customer set Name=@name where Id=@id",
new {id, name});
