Hi,

Can anyone tell me the correct way to handle unicode over the
dsql api?

Does the API return true unicode 2byte/16bit characters (cast the
char* to wchar_t* and divide sqllen by 2)

OR

Does the API return a UTF8 string (variable length characters of
1 to 3 bytes in length).


I have been assuming the first option, but this fails when reading
most string fields from metadata tables (since most are declared as
UNICODE_FSS. Is the problem simply that the metadata field
characteristics lie about the character set, or is there something
I am missing?


--
Geoff Worboys
Telesis Computing