Sure thing. I need to figure out how to execute the startup code so the user doesn't have to wire it into their app startup. I hate that Dapper requires this.
FWIW I am currently calling this as part of opening the connection. The result is a noop since the method checks if the typehandler already exists in the SqlMapper.typeHandlers dictionary.
Looks something like this:
let registerTypeHandlers() =
SqlMapper.AddTypeHandler(OptionHandler<Guid>())
SqlMapper.AddTypeHandler(OptionHandler<int64>())
...
let dbConnect string =
registerTypeHandlers()
new OracleConnection(string)
PS: Am also forced to use Oracle, so would be nice to make that an option :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for this!
I had the project on hold that could use this, but am restarting it now.
I currently have bits of code from your blogpost, plus other bits I scrapped together, as I discover things I need.
When it settles down I will try and switch to SlimSql... and perhaps add a PR or two :)
Sure thing. I need to figure out how to execute the startup code so the user doesn't have to wire it into their app startup. I hate that Dapper requires this.
FWIW I am currently calling this as part of opening the connection. The result is a noop since the method checks if the typehandler already exists in the SqlMapper.typeHandlers dictionary.
Looks something like this:
PS: Am also forced to use Oracle, so would be nice to make that an option :)