Paul Charlton

PR is forthcoming

see also: https://github.com/rails-sqlserver/tiny_tds/issues/461#issuecomment-599680834

changed to [WIP] to add unit tests for additional parameters and checks for the type coercion expected values

@wpolicarpo thanks for asking! --- it has been more of a bandwidth issue and getting distracted with other things -- if you need it sooner, by all means add some...

@aharpervc is the tagging process manual, or partly automated? seems like there should be a Gemfile.lock updated at the time of tagging so that we can get reproducible builds of...

I already started testing a WIP PR for this ... new unit tests first. `:use_utf16` is closer in behavior, but still not consistent with rails handling of underlying database fields,...

wrote up an issue for `rails/rails` to address the ability to `unset` or remove a config key via the contents of DATABASE_URL here -> https://github.com/rails/rails/issues/38748

@aharpervc good point see: https://github.com/rails/rails/issues/9097#issuecomment-14023312 and https://github.com/rails/rails/commit/e54acf1308e2e4df047bf90798208e03e1370098 which explicitly defer type-coercion into the adapter layer -- however, the config option needs to be a config option key that the adapter...

@aharpervc after looking through the code in the activerecord-sqlserver-adapter, I concur that it should be responsible for the type-casting as it is already reading (aka `first use`) those values from...

another thought -- usually when I have two (or more) pieces of code that need a shared understanding of data format, I write a schema and then either a code...