From: K J Cheetham <jamie@shadowcatsystems.co.uk>
Date: Fri, 1 Jun 2007 12:46:41 +0000 (+0000)
Subject: pod tweaking for line wrappings
X-Git-Tag: v0.08010~150^2~26
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=0aff97c2eadba0afcf08e25984292bd1c2a36135;hp=f5d3a5def17ae78dd9d478e1c71736b33e591edb;p=dbsrgits%2FDBIx-Class.git

pod tweaking for line wrappings
---

diff --git a/lib/DBIx/Class/Storage/DBI/Replication.pm b/lib/DBIx/Class/Storage/DBI/Replication.pm
index 98779a6..c64cad5 100644
--- a/lib/DBIx/Class/Storage/DBI/Replication.pm
+++ b/lib/DBIx/Class/Storage/DBI/Replication.pm
@@ -30,20 +30,25 @@ DBIx::Class::Storage::DBI::Replication - EXPERIMENTAL Replicated database suppor
 Warning: This class is marked EXPERIMENTAL. It works for the authors but does
 not currently have automated tests so your mileage may vary.
 
-This class implements replicated data store for DBI. Currently you can define one master and numerous slave database
-connections. All write-type queries (INSERT, UPDATE, DELETE and even LAST_INSERT_ID) are routed to master database,
-all read-type queries (SELECTs) go to the slave database.
+This class implements replicated data store for DBI. Currently you can define
+one master and numerous slave database connections. All write-type queries
+(INSERT, UPDATE, DELETE and even LAST_INSERT_ID) are routed to master
+database, all read-type queries (SELECTs) go to the slave database.
 
-For every slave database you can define a priority value, which controls data source usage pattern. It uses
-L<DBD::Multi>, so first the lower priority data sources used (if they have the same priority, the are used
-randomized), than if all low priority data sources fail, higher ones tried in order.
+For every slave database you can define a priority value, which controls data
+source usage pattern. It uses L<DBD::Multi>, so first the lower priority data
+sources used (if they have the same priority, the are used randomized), than
+if all low priority data sources fail, higher ones tried in order.
 
 =head1 CONFIGURATION
 
 =head2 Limit dialect
 
-If you use LIMIT in your queries (effectively, if you use SQL::Abstract::Limit), do not forget to set up limit_dialect (perldoc SQL::Abstract::Limit) by passing it as an option in the (optional) hash reference to connect_info.
-DBIC can not set it up automatically, since it can not guess DBD::Multi connection types.
+If you use LIMIT in your queries (effectively, if you use
+SQL::Abstract::Limit), do not forget to set up limit_dialect (perldoc
+SQL::Abstract::Limit) by passing it as an option in the (optional) hash
+reference to connect_info.  DBIC can not set it up automatically, since it can
+not guess DBD::Multi connection types.
 
 =cut
 
@@ -82,7 +87,8 @@ sub connect_info {
 	pop @{$info->[0]};
     }
 
-    # We need to copy-pass $global_options, since connect_info clears it while processing options
+    # We need to copy-pass $global_options, since connect_info clears it while
+    # processing options
     $self->write_source->connect_info( [ @{$info->[0]}, { %$global_options } ] );
 
     @dsns = map { ($_->[3]->{priority} || 10) => $_ } @{$info}[1..@$info-1];