[egenix-users] Impossible to correct execute stored procedure
mal at egenix.com
Wed Nov 5 16:04:08 CET 2008
On 2008-11-05 15:55, Sirio Capizzi wrote:
> M.-A. Lemburg ha scritto:
>> mxODBC 3.0 tries to use the ODBC 3.x API where possible,
>> so that may explain why you are seeing different behavior
>> compared to mxODBC 2.0.
>> The SQL Server 2000 ODBC driver is rather old, so it's possible
>> that it doesn't support the ODBC 3.x API all that well.
>> However, our tests pass just fine for that driver as well, but
>> AFAIK we don't use cursors in the tested stored procedures, so
>> that's something to add to the test suite.
> Very interesting... It is possible to force mxODBC to use only the ODBC
> 2.0 API? There are newer drivers for SQL Server 2000?
No that's not possible without patching mxODBC.
The ODBC manager will normally translate between the application and the
driver, however, it only does this if the driver itself advertises itself
as being a 2.0 driver.
We'll setup a few new tests to try to reproduce the problem.
>> Could you send us an ODBC trace that shows the crash (ie. stops
>> after the crash) ?
> Of course, you will find it in the attachment. Thank you for your help.
Professional Python Services directly from the Source (#1, Nov 05 2008)
>>> 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 mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX 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