I didn’t say at all that ODBC.jl now couldn’t handle it, but back in June 2015, it wasn’t nearly ready yet.
Efficient support for strings (esp. being able to use UTF-16 strings, and handling things like UTF-8 variants correctly) and decimal numbers was (and still is!) very important for us. Back at the time, I did communicate those issues to @quinnj,
and as I said earlier, I know he’s done quite a lot to improve ODBC.jl and JSON.jl since I first met him at JuliaCon 2015.
Since then, we haven’t (yet) had time to evaluate whether ODBC.jl could now support all our requirements, or if it would work better for us than our “home-rolled” solutions.
(Personally, I’d like to move to ODBC.jl and PostgreSQL.jl, to cut down on our maintenance of our own code, and better spend that time on improving those packages for everybody’s benefit)