Closed kaaja-h closed 1 year ago
Hi @kaaja-h, hmmm... I've never thought about it. Probably in the next version, I would have to add Type registration on the dbvendor-type level. Will look at it.
Workaround, for now, is to create your own handlers function and not call the Dapper.FSharp ones
Published in the new version - now there should be one registration per db vendor
When using sqlite you have to register types using this way
but you register some type converter more than once. For example TimeSpan option I found that dapper sometime select convertor from OptionTypes.register() and sometime from addSQLiteTypeHandlers(). For example for TimeSpan it is problem, because convertor from OptionTypes.register() don't use TimeSpan.Parse and throws exception.