On Thu Jul 11 08:07:45 2024 +0000, Hans Leidekker wrote:
Are you using the ANSI or Unicode driver? (Also, shall we address this at a later point? I don't think it's relevant to this MR).
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.