On 07-10-2016, Konstantin Khomoutov wrote: > On Thu, 6 Oct 2016 20:24:47 +0000 (UTC) > wilk <w...@flibuste.net> wrote: > >> I know... but i must access to MSACCESS database. I would like to use >> Go instead of Python. >> I found alexbrainman/odbc and it works. I found some litle issues >> that I submited to the project but I think I can workaround. >> >> Before I continue to dig, are there others Gophers using MSACCESSÂ ? >> In production ? > > I'm not doig this, but I'm pretty sure using its native drivers through > ODBC is pretty much the most sensible way to go about dealing with your > task. And that alexbrainman/odbc driver is of good quality and is well > maintained.
Fine, I'm confident of the quality of this driver, I'll continue to try. > > Well, in theory, you could take another route and write some low-level > glue code in C++ to use the OLE DB "Jet database" drivers, and then > make use of that code in your Go project (on Windows, you could avoid > using `cgo` by building a DLL with your glue code and accessing it from > Go using the same way alexbrainman/odbc deals with ODBC DLLs). > I'm afraid this is too much work for too little gain though. > So I'd go with ODBC untill you encounter some major unfixable roadblock > going that way. > > It could also be possible to use the MS Jet DLL directly but I'm again > afraid that would be even more work that accessing it through OLE DB > layer. I'm happy that there are other possibilities. But I'm affraid to be alone using MSACCESS with Go. Even if I understand that nobody want to invest in this. -- William -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
