FreeTDS Development Group

["ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>]

> Well, thank you for clarifications. I would be satisfied with 
> SQL_WVARCHAR
> support a la blobs - no convertions or special treatment, 
> just -8 and -9
> data types codes and raw data. But OK, we have already 
> resigned ourselves to
> loosing the unicode support.
> 

Mmm... you you want to simplify works a lot there are some possibility:
- do not support *W functions
- do not support input/output parameters (placeholders in
SQLExecDirect/SQLExecute)
- support SQL_W(VAR)CHAR/SQL_C_WCHAR for SQLFetch/SQLBindCol
- keep WCHAR as they are and read as binary data

Using these restriction I don't think the change will reach 100 rows of
code... some if in token.c and some case conditions in odbc code (threat
WCHAR as binary...)

freddy77