Re: long way to WCHAR...

"Frediano Ziglio" <[email protected]>
Newsgroups gmane.comp.db.tds.freetds
Message-ID <[email protected]>
>
> Today I commited some patch for SQL_C_WCHAR/SQL_(VAR)CHAR.
> Although not complete there was many improvements. Now libTDS
> is set so it doesn't convert
> strings but conversion occurs in ODBC in SQLFetch/SQLGetData.
> This lead to some
> differencies:
> - client utf8 encoding comsume less space
> - conversions to SQL_C_BINARY returns unconverted strings,
> this is compliant to MS
> behavior
> - in indicator we can have SQL_NO_TOTAL meaning there is more
> data to read but we don't
> know how much, this could break some compatibility
> Mostly tests works except utf8 (see
> http://freetds.sourceforge.net/up/out83/test/, only
> utf8 fails for conversion issues) but I should commit another
> patch that fix the problem.
>
> Note however that tests for new types are not complete with
> SQL_C_WCHAR complitely
> missing.
>
> So... stay tuned :)
>

As somebody should have see there were a lot of commits about SQL_C_WCHAR.

Current status is much better:
- odbc_tds2sql is ok in all cases!
- odbc_sql2tds behave much better the only missing conversion is from WCHAR
to fixed type.
There are however a lot of cases to review like binary blobs and some
SQLGetData/SQLPutData issues

freddy77
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.