title: Can Dapper handle nullable boolean/bit fields? [INVALID]
body: <p>I'm trying to use Dapper for the first time, but I've immediately run into the problem in that it doesn't seem that Dapper can handle nullable fields. This surprises me greatly as these are extremely common. </p>
  
  <p>If I have a nullable boolean field in my SQL Server database and try and use Dapper to populate the nullable boolean property on my C# class, an exception is thrown if the boolean field contains a null value:</p>
  
  <pre><code>System.FormatException: String was not recognized as a valid Boolean.
  </code></pre>
  
  <p>Is there any fix or workaround for this?  I find it hard to believe Dapper can't handle this as it looks like it's been around for  a while and this is an extremely basic function.</p>
  
  <p><strong>EDIT:  This was my mistake!  My column was actually a nvarchar which happened to contain 0 or 1, and as such, I hadn't noticed. Changing it to BIT (or the C# property to "string?") fixes the problem.</strong></p>