[fpc-devel] TStringField, String and UnicodeString and UTF8String
joshyfun at gmail.com
Thu Jan 13 10:32:00 CET 2011
Thursday, January 13, 2011, 10:03:02 AM, you wrote:
>> ODBC 3.5 was launched around 2000-2001.
L> But this approach will require changes in packages/odbc/src/odbcsql.inc
L> like, does not ?:
L> - pointer(SQLGetData) :=
L> + pointer(SQLGetData) :=
L> And I do not know how it affect compatibility for example in UNIX or if
L> all ODBC drivers support this functionality.
Most probably it needs a "flag" to indicate that the ODBC must work in
Unicode, and then dynamic link to *W functions if this flag is set. I
think ODBC drivers since 2002+/- should have this set of APIs, but I
had never used ODBC in my life... :)
L> But also in this case we will get UTF-16 widestrings (in Windows) not
L> UTF-8, does not ?
That's not important, you get unicode in the specified by the API
format, then SQLConnector fills information in the expected target
format (WideString, UTF8String over AnsiString, Raw bytes...).
More information about the fpc-devel