Committed by Greg Sabino Mullane <[email protected]> Better AutoCommit docs. RT 82356
--- Changes | 3 +++ Pg.pm | 6 ++---- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/Changes b/Changes index 7088de0..8596b43 100644 --- a/Changes +++ b/Changes @@ -4,12 +4,15 @@ Version ??? + - Adjust lo_import_with_oid check for 8.3 (CPAN bug #83145) + - Better handling of libpq errors to return SQLSTATE 08000 (Stephen Keller) - Make sure CREATE TABLE .. AS SELECT returns rows in non do() cases. [GSM] - Spelling fix per CPAN bug #78168 + - Better wording for the AutoCommit docs (CPAN bug #82536) Version 2.19.3 Released August 21, 2012 (git commit be018f10fdaf4163f98affcb7244046e8f47420d) diff --git a/Pg.pm b/Pg.pm index 3a83927..86a0bfb 100644 --- a/Pg.pm +++ b/Pg.pm @@ -3794,10 +3794,8 @@ complete definition of C<AutoCommit> please refer to the DBI documentation. According to the DBI specification the default for C<AutoCommit> is a true value. In this mode, any change to the database becomes valid immediately. Any -C<BEGIN>, C<COMMIT> or C<ROLLBACK> statements will be rejected. DBD::Pg -implements C<AutoCommit> by issuing a C<BEGIN> statement immediately before -executing a statement, and a C<COMMIT> afterwards. Note that preparing a -statement is not always enough to trigger the first C<BEGIN>, as the actual +C<BEGIN>, C<COMMIT> or C<ROLLBACK> statements will be rejected. Note that +preparing a statement does not always contact the server, as the actual C<PREPARE> is usually postponed until the first call to L</execute>. =head2 Savepoints -- 1.7.1
