Minor messing with syntactically incorrect POD (no =headX blocks inside =begin, and...

[dbsrgits/DBIx-Class-Historic.git] / lib / DBIx / Class / Storage.pm

diff --git a/lib/DBIx/Class/Storage.pm b/lib/DBIx/Class/Storage.pm
index e317d1f..d72840f 100644 (file)
--- a/lib/DBIx/Class/Storage.pm
+++ b/lib/DBIx/Class/Storage.pm
@@ -460,27 +460,29 @@ sub svp_rollback {
   $exec->($self, $name);
 }
 
-=for comment
+=begin comment
 
-=head2 txn_scope_guard
+    =head2 txn_scope_guard
 
-An alternative way of transaction handling based on
-L<DBIx::Class::Storage::TxnScopeGuard>:
+    An alternative way of transaction handling based on
+    L<DBIx::Class::Storage::TxnScopeGuard>:
 
- my $txn_guard = $storage->txn_scope_guard;
+     my $txn_guard = $storage->txn_scope_guard;
 
- $row->col1("val1");
- $row->update;
+     $row->col1("val1");
+     $row->update;
 
- $txn_guard->commit;
+     $txn_guard->commit;
 
-If an exception occurs, or the guard object otherwise leaves the scope
-before C<< $txn_guard->commit >> is called, the transaction will be rolled
-back by an explicit L</txn_rollback> call. In essence this is akin to
-using a L</txn_begin>/L</txn_commit> pair, without having to worry
-about calling L</txn_rollback> at the right places. Note that since there
-is no defined code closure, there will be no retries and other magic upon
-database disconnection. If you need such functionality see L</txn_do>.
+    If an exception occurs, or the guard object otherwise leaves the scope
+    before C<< $txn_guard->commit >> is called, the transaction will be rolled
+    back by an explicit L</txn_rollback> call. In essence this is akin to
+    using a L</txn_begin>/L</txn_commit> pair, without having to worry
+    about calling L</txn_rollback> at the right places. Note that since there
+    is no defined code closure, there will be no retries and other magic upon
+    database disconnection. If you need such functionality see L</txn_do>.
+
+=end comment
 
 =cut