https://bugs.winehq.org/show_bug.cgi?id=54499
--- Comment #3 from Hans Leidekker hans@meelstraat.net --- (In reply to Alistair Leslie-Hughes from comment #2)
(In reply to Hans Leidekker from comment #1)
(In reply to Alistair Leslie-Hughes from comment #0)
Wine is unable to user native ODBC drivers which have been installed. PostgreSQL and MySQL are two of the comment ones.
I guess you mean the Windows versions of the ODBC drivers. IIRC you can use them if you install native MDAC and add a couple of overrides.
MDAC only supports 32bit and is a standard component I install for ODBC support but since moving to 64bits it's not longer a viable option.
This is a good reason to change Wine to use Windows drivers.
Wouldn't we loose integration with host configuration of the drivers? Do all relevant databases currently supported through unixODBC have a Windows driver?
Yes we would loose integration to the host configuration.
That's unfortunate but I guess most users would set up unixODBC drivers specifically for use with Wine. They would just need to switch to Windows drivers. Users who shared a configuration with Unix apps will somehow need to synchronize though.
To my knowledge most database vendors who support windows would have a ODBC driver. From experience all the database I've used, both free and commercial have a windows driver of some sort.
I guess it's reasonable to assume that if there's a unixODBC driver for a given database a corresponding Windows driver exists as well.
Currently the only way is to install the unixODBC driver, you require which isn't always free.
Can you elaborate on this? When isn't it free?
The "Microsoft SQL Server" driver isn't free to use with unixODBC for example.
It's still not clear to me. You mean it costs money to use unixODBC driver for Microsoft SQL Server? Is that different from the Windows driver?