Re: [Firebird-odbc-devel] SQLxxxW functions

[Dimitry S. <sd...@ib...>]

04.02.2013 12:10, Jojakim wrote:
> But my question was, how these fields are (or should be) used in the driver
> sources. Is this like the standard, or do they have some internal meanings or
> special treatments in special cases. And how should they be set up from the
> FBs meta data info.

   It depends on coercion between FB data types and ODBC C-types. If, for example, 
SQL_VARYING is coerced to SQL_C_WCHAR, and FB character set is UTF8, octets length should 
be = sqllen/2, display length = sqllen/4. For single-byte character sets octets length = 
sqllen*2, display length = sqllen.
   Of course, all this in case if WCHAR is stay for UCS2. For UTF-16 I have no idea whet 
to do if some characters in FB data ends up in four bytes in UTF-16 and how to detect it.

-- 
   WBR, SD.