Nirgal
2011-08-25 19:28:50 UTC
I had a look at the recent changes in odbc, and could finally test it.
I encountered a batch of problems with the unicode functions:
Some clients like pyodbc really don't like the fact that some wide functions are missing: It wants all of them or none of them.
Also, the code assume we are a little endian platform, with a lot casts of pointer to numbers of different sizes.
The patch attached enclose the W functions in a #ifdef ENABLE_ODBC_W that is *disabled* by default. I'm affraid we'll get too many problems otherwise. It also fixed some of the problems if you enable the macro.
Does anyone know how to add some nice parameters to libtools?
Right now, you need to add a -D to compile flags if you want wide odbc. Utf8 is usually enough IMHO.
I encountered a batch of problems with the unicode functions:
Some clients like pyodbc really don't like the fact that some wide functions are missing: It wants all of them or none of them.
Also, the code assume we are a little endian platform, with a lot casts of pointer to numbers of different sizes.
The patch attached enclose the W functions in a #ifdef ENABLE_ODBC_W that is *disabled* by default. I'm affraid we'll get too many problems otherwise. It also fixed some of the problems if you enable the macro.
Does anyone know how to add some nice parameters to libtools?
Right now, you need to add a -D to compile flags if you want wide odbc. Utf8 is usually enough IMHO.