[egenix-users] OperationalError 08S01

[M.-A. Lemburg]

Michal Vitecek wrote:
>  hello everyone,
> 
>  i am using mxODBC version 2.1.0b2 directly connected to Solid (so no
>  FreeTDS or unixODBC in between). now when my code tries to update a
>  column with a long string (64252 characters) i get the following:
> 
>     OperationalError ('08S01', 0, 'Communication link failure', 5835): [traceback]
> 
>  i'm positive the connection to the DB hasn't timed out, the column
>  updated is defined as LONG VARCHAR (262144) (256kb). when the length of
>  the string is decreased all goes well but with a string of length 64252
>  the above exception is raised all the time.
> 
>  is there any 64kb limit in mxODBC?

No, but this sounds a lot like a bug in the Solid ODBC
driver or a missing setting in its configuration.

Some database drivers limit the network paket size to 64kB
and this will then cause errors like the one you are seeing.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Oct 21 2005)
>>> 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,FreeBSD for free ! ::::