[freetds] dbsqlexec() blocks for ever where database conecti on is lost
Lowden, James K
LowdenJK at bernstein.com
Tue Apr 1 12:57:49 EST 2003
> From: GUTIERREZ Pablo TESIS-TAMSA [mailto:tesgup at tamsa.com.mx]
> Sent: March 31, 2003 6:20 PM
> 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() ).
There are people looking at dbpoll(). It will require some reworking of the
socket handling. I wouldn't be surprised to see dbsettime() implemented
along the way.
> 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
I think you will find that's fixed in 0.61. I know it was worked on and
I would be happy to add QNX to our "runs on" list. If you could merge your
changes into a recent snapshot and send us a patch, perhaps we could include
them in future releases. Then, when dbpoll() is ready, you won't be
confronted with another porting effort.
The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.
More information about the FreeTDS