From: Daniel Gruno <humbedooh@apache.org>
Date: Tue, 3 Apr 2012 06:47:12 +0000 (+0000)
Subject: Merge r1308718 from trunk:
X-Git-Tag: 2.4.2~26
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=8e8b2438e2acf236dfec3a3574cf6f411db541bf;p=apache

Merge r1308718 from trunk:
Added a note about MySQL's reconnect option and its effects on prepared statements

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1308720 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/mod_dbd.xml b/docs/manual/mod/mod_dbd.xml
index 3021e29883..74b1f4d219 100644
--- a/docs/manual/mod/mod_dbd.xml
+++ b/docs/manual/mod/mod_dbd.xml
@@ -112,6 +112,14 @@ APR_DECLARE_OPTIONAL_FN(void, ap_dbd_prepare, (server_rec*, const char*, const c
     <p>It is up to dbd user modules to use the prepared statements
     and document what statements can be specified in httpd.conf,
     or to provide their own directives and use <code>ap_dbd_prepare</code>.</p>
+	
+	<note type="warning"><title>Caveat</title>
+	When using prepared statements with a MySQL database, it is preferred to set
+	<code>reconnect</code> to 0 in the connection string as to avoid errors that
+	arise from the MySQL client reconnecting without properly resetting the
+	prepared statements. If set to 1, any broken connections will be attempted
+	fixed, but as mod_dbd is not informed, the prepared statements will be invalidated.
+	</note>
 </section>
 
 <section id="security">