FreeTDS Development Group

["James K. Lowden" <jklowden AT freetds.org>]

Dan Mohn wrote:
>  I am physically
> unplugging the network cable.  Like;
> 
> send sql statement
> while not resultset eof
> ---here I pull the network cable after a couple of rows have been read
> ---get data
> ---check for an timeout error
> ---get the next row
> loop
> 
> Interestingly, after appx 2 hours, an error is trapped, and Realbasic is
> reporting the following error message it claims is from the odbc driver;
> 
> [FreeTDS][<drivername>]Communication link failure.
> 
> What do you recommend I do for my next step? 

Hi Dan, 

Could you please execute the same test in bsqldb?  I would like to know if
the problem is in FreeTDS or in some higher layer.  That won't necessarily
exculpate FreeTDS, but it will tell us if FreeTDS is at least internally
consistent.  

--jkl