DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39329 ------- Additional Comments From [EMAIL PROTECTED] 2007-08-22 07:33 ------- (In reply to comment #11) > Just retested this with mod_dbd from trunk (r553563) and apr-util 1.2.7 + > current apr_dbd_mysql.c compiled against MySQL 5.0.27 and everything works as > expected with no modifications. Reconnection no longer seems to be an issue as > the need for 2 mysql_pings seems to have dissapeared, see the last couple replies in > http://bugs.mysql.com/bug.php?id=9271 > but I believe for any earlier MySQL versions it will still be required. > Now the bad part is since mysql_ping in MySQL 5.0.27 (5.0.20 and later I think) > doesn't return an error anymore, just reconnects transparently, and since > prepared statements are cleared as per > http://www.mysql.org/doc/refman/5.0/en/auto-reconnect.html > I'm not sure how you can detect that a mysql_ping has done a reconnection and > reinit your prepared statements. I suppose you'd need to track the id of the > mysql connection and look for a change before and after calling apr_dbd_check_conn. I tried the patch and found something might be a performance issue. this part of the patch : + if ((rv == APR_SUCCESS) || (rv == APR_ENOTIMPL)) { + rv = dbd_prepared_init(pool, svr, rec); + break; + } gets executed even if the first apr_dbd_check_conn returns a success. Is this on purpose? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
