[egenix-users] Problem with mxodbc 3.1 and Sybase 15.5
mal at egenix.com
Wed Jan 5 01:05:30 CET 2011
Dale Arntson wrote:
> The odbc trace log is attached.
Thanks. It appears that the Sybase ODBC driver doesn't like the
fact that mxODBC always binds None (NULL) values using SQL_CHAR -
since the data type doesn't matter when passing in NULL values.
This is in line with the ODBC standard and works well with
all other ODBC drivers being used with mxODBC.
No idea why the error message says "Implicit conversion from datatype 'CHAR' to 'SMALLINT' is not
We already have a whole set of work-arounds for the Sybase
driver in mxODBC, so I suppose we'll have to find yet another
one for this particular quirk of the driver...
Regarding the other error message "The parameter of type 61 did not have a valid value."
I can't really say what's wrong here, since ODBC doesn't have a
type code 61 and the log doesn't show such a code being used either.
> On 1/4/2011 3:54 PM, M.-A. Lemburg wrote:
>> Hi Dale,
>> could you try enabling the ODBC tracing function in the Windows
>> ODBC manager and send us the ODBC log ?
>> Here's the documentation on how to enable tracing in the
>> MS ODBC Manager:
>> If standard tracing doesn't work, you could try the
>> Visual Studio Analyzer:
Professional Python Services directly from the Source (#1, Jan 05 2011)
>>> Python/Zope Consulting and Support ... http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
::: Try our new mxODBC.Connect Python Database Interface for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
More information about the egenix-users