On Thu Jul 11 07:26:20 2024 +0000, Hans Leidekker wrote:
That will not work without conversion of string attributes. If the app uses a data source configured for the Unicode driver but calls ANSI functions then we should probably convert. I don't expect this to be common though. If it's the other around then the conversion would be lossy. This would need some tests.
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.