FreeTDS Development Group

[Brian Bruns <camber AT ais.org>]

The proper behaviour would be to throw a client error message (OpenClient 
says something about dbprocess dead or some such).  This would happen 
generally upon exhaustion of remaining data.  A smart application can 
actually be designed to catch the error and attempt to reopen the 
connection inside the error handler, we have done that in the pase where I 
work (it's great for HA clusters were it takes a minute or two for the 
failover box to restart the database).

I'll see if I can't look up the error number.

Brian

On Mon, 18 Mar 2002, Steve Willer wrote:

> 
> On Fri, 15 Mar 2002, James Cameron wrote:
> 
> > I started in on this and hesitated ... is it correct for it to return
> > what it has even if the connection has closed or failed?  Code above
> > this point returns -1.
> 
> I would tend to think a situation like this should ultimately report a
> fatal error on the connection. But I don't know how to do that, and I
> thought at the very least FreeTDS should detect the error condition.
> 
> 
> ---
> You are currently subscribed to freetds as: [camber AT ais.org]
> To unsubscribe, forward this message to $subst('Email.Unsub')
>