X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FDBIx%2FClass%2FRelationship.pm;h=22be1d319ca9b70a7780e45c297f8f5c3d091ff0;hb=561bd5f683f616706dd059ea3330f6abfd10eb26;hp=cdb35811c573d9a5c30358e064e3de077c05fd1c;hpb=8452e496adea0c57b81f413e11b2f5b5b6e62c5c;p=dbsrgits%2FDBIx-Class.git

diff --git a/lib/DBIx/Class/Relationship.pm b/lib/DBIx/Class/Relationship.pm
index cdb3581..22be1d3 100644
--- a/lib/DBIx/Class/Relationship.pm
+++ b/lib/DBIx/Class/Relationship.pm
@@ -97,10 +97,14 @@ between C<has_one> and C<might_have> is that C<has_one> uses an (ordinary) inner
 whereas C<might_have> uses a left join.
 
 
-=head2 many_to_many                                                             
-                                                                                
-  __PACKAGE__->many_to_many( 'accessorname' => 'a_to_b', 'table_b' );           
-  my @f_objs = $obj_a->accessorname;                                            
+=head2 many_to_many
+
+  __PACKAGE__->many_to_many( 'accessorname' => 'a_to_b', 'table_b' );
+  my @f_objs = $obj_a->accessorname;
+
+Creates an accessor bridging two relationships; not strictly a relationship
+in its own right, although the accessor will return a resultset or collection
+of objects just as a has_many would.
 
 =cut