Author: timbo Date: Mon Jul 21 12:37:50 2008 New Revision: 11560 Modified: dbi/trunk/Changes dbi/trunk/DBI.pm
Log: Clarified docs for ReadOnly thanks to Martin Evans Modified: dbi/trunk/Changes ============================================================================== --- dbi/trunk/Changes (original) +++ dbi/trunk/Changes Mon Jul 21 12:37:50 2008 @@ -59,10 +59,12 @@ Fix PERL_UNUSED_VAR for 5.6.2 - update ppport.h? No longer support 5.6? In future. (Access to recent errors in gofer http transport) +Memory leak? Fixed missing import of carp in DBI::Gofer::Execute. Added note to docs about effect of execute(@empty_array). + Clarified docs for ReadOnly thanks to Martin Evans. =head2 Changes in DBI 1.605 (svn r11434) 16th June 2008 Modified: dbi/trunk/DBI.pm ============================================================================== --- dbi/trunk/DBI.pm (original) +++ dbi/trunk/DBI.pm Mon Jul 21 12:37:50 2008 @@ -3844,8 +3844,9 @@ Note that the exact definition of 'read only' is rather fuzzy. For more details see the documentation for the driver you're using. -If the driver can make the handle truly read-only (by issuing a statement like -"C<set transaction read only>" as needed, for example) then it should. +If the driver can make the handle truly read-only then it should +(unless doing so would have unpleasant side effect, like changing the +consistency level from per-statement to per-session). Otherwise the attribute is simply advisory. A driver can set the C<ReadOnly> attribute itself to indicate that the data it
