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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|mod_dbd ap_dbd_acquire |mod_dbd reconnection and |failure |prepared statements ------- Additional Comments From [EMAIL PROTECTED] 2007-07-06 18:33 ------- 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. -- 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]
