On Thu Jul 11 22:33:35 2024 +0000, Alistair Leslie-Hughes wrote:
I'm using the unicode driver. Making the default SQLSetConnectAttrW, then we can handle the fallback later. Plus unixODBC will already handle the conversion (strings) if we pass them as unicode. Not that we are going that yet. Changing to use the ascii driver, returns values as expected (assuming text is latin based text) though none of the unicode functions are available.
The function pointer for native drivers needs to be tested before being used as it might not exist.