Home Original page

mxODBC SQL Type error with MS SQL Server

Bill Hunter bkhunter at best.com
Thu Mar 30 03:25:35 EST 2000 
The mysterious type that mxODBC cannot handle on SQL Server 7 is
"nvarchar" - unfortunately this is the default that SQL Server
attempts to use for character strings!

mxODBC works fine against fields that are not character strings, but
heck, over half my fields are nvarchar ... true for many other
people, I conjecture.   Guess I will look at some of the other ODBC
wrappers that are floating around.

How big a deal would it be to add a type to mxODBC?  And would it be
in Python or in C?

On Wed, 29 Mar 2000 18:47:30 +0530, "George Thom at s"
<georgethomas at pspl.co.in> wrote:

>Hi there,
>I had experienced the same problem ( SQL type (code -9) not implemented
>) and I reproduce below a fragment from Marc Lehmburg's
>(mal at lemburg.com)	numerous patient replies to my queries.
>
>-------------mal at lemburg.com said -------------------------
>SQL type -9 is not defined in ODBC 3.5 AFAIK. No idea what
>type this is. The next version of mxODBC will support
>unkown types by fetching them as strings, but the current
>one cannot deal with them, sorry.
>------------------------------------------------------------
>
>Personal Addendum: If you open SQLUCODE.H in the INCLUDE directory of
>your Visual Studio installation, you will find a line that reads
>
>#define SQL_WVARCHAR         (-9)
More information about the Python-list mailing list