apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bojan Smojver <bo...@rexursive.com>
Subject Re: [PATCH]: improved error reporting for apr_dbd_mysql.c (and question)
Date Thu, 18 May 2006 19:26:18 GMT
On Thu, 2006-05-18 at 01:27 -0700, Alex Dubov wrote:

> Attached patch makes apr_dbd_mysql to always return
> internal xxx_errno codes of mysql instead of arbitrary
> integers.

We should be returning APR error codes throughout DBD drivers, IMHO. The
API user may not have access to interpretation of MySQL (and other)
database specific error codes. Current behaviour is suboptimal, though.

> Question:
> After period of inactivity, mysqld will close
> connection to the server. I found no way to resume the
> connection apart of restarting the server. I'm going
> to look into this later, but may be somebody knows how
> to deal with the situation?

Isn't mysqld the server? I'm guessing you mean mysql client closes the
connection to mysqld, right? I can have a look at this on my setup, but
I haven't noticed any disconnections in my testing (MySQL 5.0).

-- 
Bojan


Mime
View raw message