|
From: Markus H. <mar...@mh...> - 2004-01-20 21:15:46
|
> is this a libdbi problem or a mysql problem ? As far as I can tell, it > happens like this: > * program opens connection to mysql server and leaves it open > * mysql server is timeout -ing and closing the connection > * program needs to query mysql server using already opened connection > * libdbi tryies to write to the connection he knew is opened and a SIGPIPE > is raised. > * nobody's happy :( > Can you give me a solution with this one ? Besides modifications in the > program to open/close connections. I'm not exactly the MySQL expert on this list, but I think this is why we've added the dbi_conn_ping() function. It is not documented yet, but the usage should be pretty obvious from the libdbi sources. All you'd have to do is to ping the server before issuing the query that crashes your app currently. If the server does not reply, open a new connection. regards, Markus -- Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |