mxODBC SQL Type error with MS SQL Server

M.-A. Lemburg mal at lemburg.com
Fri Mar 31 04:01:00 EST 2000


Bill Tutt wrote:
> 
> > From: M.-A. Lemburg [mailto:mal at lemburg.com]
> 
> > BTW, does anyone have a pointer to the specifications
> > behind the Unicode support in SQL Server or the latest
> > ODBC variant ?
> >
> 
> SQL Server 7 specific details:
> 
> Unicode constants are desginated by a N'A Unicode string' in the query
> string.
> The datatypes in SQL Server are: nchar, nvarchar, and ntext.
> All of these are UTF-16 data fields. (machine endian)
> As far as handling collation issues:
> 
> SQL Server 7 requires that character set, sort order, and Unicode collation
> be specified on a per server basis.
> 
> The details on Unicode collation support can be found at:
> http://msdn.microsoft.com/library/psdk/sql/2_006_39.htm
> 
> The ODBC C Unicode datatypes is:
> SQL_C_WCHAR
> 
> The ODBC SQL datatypes are:
> SQL_WCHAR
> SQL_WVARCHAR
> SQL_WLONGVARCHAR
> 
> The ODBC API also uses UTF-16.
> 
> For more info on the ODBC stuff:
> http://msdn.microsoft.com/library/psdk/dasdk/odch2h9h.htm

Thank you :-)

That'll make a great start for the Unicode integration into mxODBC.

-- 
Marc-Andre Lemburg
______________________________________________________________________
Business:                                      http://www.lemburg.com/
Python Pages:                           http://www.lemburg.com/python/





More information about the Python-list mailing list