11 Jul
2024
11 Jul
'24
8:07 a.m.
On Thu Jul 11 07:45:44 2024 +0000, Alistair Leslie-Hughes wrote:
Currently this causes an fault in my testing, since the driver doesn't have this function. From my experience, I'm calling ODBC32.SQLSetConnectAttrW to set values, so the driver should call the same function or handle the case where SQLSetConnectAttrW doesn't exist,eg call the ascii version. unixODBC will return an error, if a ascii function is called and only the unicode function exist. Maybe the default should be to call the SQLSetConnectAttrW.
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).