Committed by =?UTF-8?q?Dagfinn=20Ilmari=20Manns=C3=A5ker?= <[email protected]>

Fix pg_switch_prepared database handle documentation

The documentation for database handle attribute disagreed with the one
for the statement handle attribute, which was the correct one.
---
 Changes | 3 +++
 Pg.pm   | 4 ++--
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/Changes b/Changes
index 79b3781..efa28e9 100644
--- a/Changes
+++ b/Changes
@@ -21,6 +21,9 @@ Version 3.5.1
   - Documentation fix
     [Stuart A Johnston]
 
+  - Fix pg_switch_prepared database handle documentation
+    [Dagfinn Ilmari Mannsåker]
+
 Version 3.5.0  Released January 6, 2015 (git commit 
bb13d3306fd1c73fac1c0c8a330c14e6b8443942)
 
   - Allow "placeholder escaping" by the use of a backslash directly before it, 
e.g.
diff --git a/Pg.pm b/Pg.pm
index 710b803..0ba899d 100644
--- a/Pg.pm
+++ b/Pg.pm
@@ -3117,8 +3117,8 @@ PQexecParams to PQexecPrepared. In other words, when it 
will start using server-
 prepared statements (assuming all other requirements for them are met). The 
default value, 
 2, means that a prepared statement will be prepared and used the second and 
subsequent 
 time execute is called. To always use PQexecPrepared instead of PQexecParams, 
set 
-pg_switch_prepared to 1. Setting it to 0 will force DBD::Pg to use 
PQexecPrepared always - 
-this was the default behavior in versions older than 3.0.0.
+pg_switch_prepared to 1 (this was the default behavior in earlier versions). 
+Setting pg_switch_prepared to 0 will force DBD::Pg to always use PQexecParams.
 
 =head3 B<pg_placeholder_dollaronly> (boolean)
 
-- 
1.8.4

Reply via email to