Markus Klein
Markus Klein
Looking at this it is more likely that somehow binary and character size is confused. I just do not know there. Yet, likely the system local is innocent. Would you...
You can log to standard error using:
I could reproduce the Bug. > Only happens on Linux. Could also be a bug with MSFT's ODBC Driver, but I guess MSFT does not do bugs 😉 Actually MSFT...
As a workaround I'll give it a try to supply larger buffers than requested by the drivers ...
To be fair to Microsoft, the function in question `SQLDescribeCol` is document to return the length in characters not bytes. . Yet it is clearly intended to determine buffer lengths...
Maybe not, depends if ADO relies on ODBC. Also relies on how wasteful authors of these libs are then using memory. I could avoid a lot of trouble if I...
> NameLengthPtr [Output] Pointer to a buffer in which to return the total number of characters (excluding the null termination) available to return in *ColumnName. If the number of characters...
It confuses binary buffer length and character length. Very likely related to the bug in question.
Definitly this. If you want to see it fail under windows too, you can use a character in the column name which is 4 Bytes in UTF-16 instead of two....
Sadly allocating larger buffers is not a suitable workaround. The drivers only copy the bytes in the length of character data in the application provided buffers. The "good" news is...