From 793db0c693b6c367663bacc0417d68ba3f2abed5 Mon Sep 17 00:00:00 2001 From: Daniel Gruno Date: Tue, 3 Apr 2012 06:47:24 +0000 Subject: [PATCH] Rebuild git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1308721 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_dbd.html.en | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/manual/mod/mod_dbd.html.en b/docs/manual/mod/mod_dbd.html.en index 0f23f3f06c..73865225de 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

-- 2.40.0