go-mssqldb VS odbc

Where does the sql server one come from and what is it? I tried https://github.com/denisenkom/go-mssqldb and maybe im jsut tired from staring at this stuff half the day but i couldnt get it to work

I switched to the "denisnkom" driver (https://github.com/denisenkom/go-mssqldb) as the stability of that improved.

I am using github.com/denisenkom/go-mssqldb package to get data from SQL Server. After querying the data, I am scanning each row and filling up a struct array. While doing so I noticed that the datetime fields in SQL Server which have 00:00:00.000 as the time value for a date time column, truncates the milliseconds (or ignores the milliseconds). Did anyone face this issue and how did you resolve it?

I started out using the ODBC driver wrapper when there weren't good choices for native drivers. I wrote a little helper package to figure out the best ODBC driver to use: https://github.com/billgraziano/mssqlodbc. Lots of the code I wrote would run in different environments with different configurations. That package is a little out of date now.

Avoiding CGO is not a reasonable request in this case. In Windows, only one process can have a file open at a time, so if multiple processes are going to access a file, it must be mediated by a server-type process that owns the file, or by serializing access with file-level locking. Since the latter would require built-in support in the software already, you are left with what Access uses - which is system-mediated driver access through either ODBC or ADODB. https://github.com/alexbrainman/odbc https://github.com/bennof/accessDBwE

I was trying to build a static binary for Linux that includes ODBC (which needs cgo) inside of it and was failing to do that. This is the library I'm trying to build with https://github.com/alexbrainman/odbc .