There was a small issue when SplinOn spaces between commas, for example: splitOn: "AddressId, Id". For more info see: http://stackoverflow.com/questions/11042618/dapper-multi-mapping-issue I have modified below line of code: From: var currentSplit = splits[splitIndex]; To: var currentSplit = splits[splitIndex].Trim(); Also added a test called: TestMultiMappingWithSplitOnSpaceBetweenCommas()
…oming from templates
…ant to store `7` as a bool - that causes problems sometimes.
… properties declared.
…oids issues on databases that return 1 as bigint by default, etc
tweak tests to represent this (and workaround) Added [ActiveTest] to allow trivial debugging individual tests
Fix for issue #70 (http://code.google.com/p/dapper-dot-net/issues/detail?id=70) and also related MS bug with DbType.Time (https://connect.microsoft.com/VisualStudio/feedback/details/381934/sqlparameter-dbtype-dbtype-time-sets-the-parameter-to-sqldbtype-datetime-instead-of-sqldbtype-time).
…) to be treated directly as a parameter
…ethod when subclassing for TVPs
…calc" is, it turns out, stupid.
Replicated a bug 'Dapper MultiMap doesn't work with splitOn with NULL value' reported on SO http://stackoverflow.com/q/10744728/449906. Dapper doesn't create an instance of the class if the first property after split is mapped to a column with NULL value.
…s) that they work fine for regular T with an enum / nullable-enum member
Now we choose by accessibility level, with importance: public > internal == protected > private and then by number of arguments: giving priority to the argumentless constructor.