From: Wallace Reis Date: Sat, 22 Mar 2008 14:28:43 +0000 (+0000) Subject: pod fixes X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=c64db0f42b79d76153064d3226d4f30a606ef893;p=dbsrgits%2FDBIx-Class-Historic.git pod fixes --- diff --git a/lib/DBIx/Class/Storage/DBI.pm b/lib/DBIx/Class/Storage/DBI.pm index 4f3416c..64a0f04 100644 --- a/lib/DBIx/Class/Storage/DBI.pm +++ b/lib/DBIx/Class/Storage/DBI.pm @@ -442,16 +442,16 @@ whether any options are specified in the new C. Another Important Note: DBIC can do some wonderful magic with handling exceptions, -disconnections, and transactions when you use C +disconnections, and transactions when you use C<< AutoCommit => 1 >> combined with C for transaction support. -If you set C in your connect info, then you are always +If you set C<< AutoCommit => 0 >> in your connect info, then you are always in an assumed transaction between commits, and you're telling us you'd like to manage that manually. A lot of DBIC's magic protections go away. We can't protect you from exceptions due to database disconnects because we don't know anything about how to restart your transactions. You're on your own for handling all sorts of exceptional -cases if you choose the C path, just as you would +cases if you choose the C<< AutoCommit => 0 >> path, just as you would be with raw DBI. Examples: