L> Yes in UNIX world it may be so (I do not know),
L> but in Windows ODBC we have no such possibility AFAIK
Quote from Microsoft:
"The ODBC 3.5 (or higher) Driver Manager supports both ANSI and
Unicode versions of all functions that accept pointers to character
strings or SQLPOINTER in their arguments. The Unicode functions are
implemented as functions (with a suffix of W), not as macros. The ANSI
functions (which can be called with or without a suffix of A) are
identical to the current ODBC API functions."
ODBC 3.5 was launched around 2000-2001.
But this approach will require changes in packages/odbc/src/odbcsql.inc
like, does not ?:
- pointer(SQLGetData) :=
GetProcedureAddress(ODBCLibraryHandle,'SQLGetData');
+ pointer(SQLGetData) :=
GetProcedureAddress(ODBCLibraryHandle,'SQLGetDataW');
And I do not know how it affect compatibility for example in UNIX or if
all ODBC drivers support this functionality.
But also in this case we will get UTF-16 widestrings (in Windows) not
UTF-8, does not ?
-Laco.
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
