FreeTDS Development Group

["Michael Kochetkov" <Michael.Kochetkov AT synartra.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)
I am afraid I will not be able to insert, update or search for unicode
strings if I have no SQL_W(VAR)CHAR placeholders.

> - 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...)
It seems that we are predisposed to wait for the official 3.5 specification
support. Moreover Unix platform is not our primary one.

Thank you,
-
Michael Kochetkov.