[freetds] dbsqlexec() blocks for ever where database conecti on is lost

ZIGLIO Frediano Frediano.Ziglio at vodafoneomnitel.it
Tue Apr 1 04:04:00 EST 2003

> Hi everybody
> We ported FREE TDS 0.60 to QNX 4.25 and we are using the 
> DB-Library API to
> connect to a SQL SERVER 2000 server.
> In the API status appears that function dbsettime() is not 
> implemented yet
> (nor are present the non-standard functions  dbpoll() or 
> dbdataready() ).
> The problem is that when you call dbsqlexec()/dbsqlok() on a 
> database that
> has just gone offline (i.e after calling dbopen() 
> successfully), it blocks
> indefinitely (even if I return INT_EXIT or INT_CANCEL from the error
> handler).
> How can I prevent it from becoming blocked? 
> Is there any form to detect that a database went offline 
> before calling
> dbsqlexec()? What if the lost of connection happens at the same time
> dbsqlexec() is running?
> Regards
> Eng. Pablo Gutierrez

If I remember this was fixed on 0.61...



This message may contain confidential and proprietary material for the sole
use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient please contact
the sender and delete all copies.
The contents of this message that do not relate to the official business of
our company shall be understood as neither given nor endorsed by it."


More information about the FreeTDS mailing list