From: Daniel Gruno Date: Tue, 3 Apr 2012 06:45:01 +0000 (+0000) Subject: Rebuild X-Git-Tag: 2.5.0-alpha~7264 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=fc6d3aab646aa5f1b513f96e31f2354ab4f3a08c;p=apache Rebuild git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1308719 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_dbd.html.en b/docs/manual/mod/mod_dbd.html.en index dd531e96e4..a4e342302d 100644 --- a/docs/manual/mod/mod_dbd.html.en +++ b/docs/manual/mod/mod_dbd.html.en @@ -130,6 +130,14 @@ APR_DECLARE_OPTIONAL_FN(void, ap_dbd_prepare, (server_rec*, const char*, const c

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 ap_dbd_prepare.

+ +

Caveat

+ When using prepared statements with a MySQL database, it is preferred to set + reconnect 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. +
top

SECURITY WARNING