X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FDBIx%2FClass%2FRelationship.pm;h=22be1d319ca9b70a7780e45c297f8f5c3d091ff0;hb=5e8b1b2adbc7b67dc7948a41354e36ce0c7998c6;hp=71c000440d3d2c73582f5a5b66c9f4f53417d01b;hpb=4685e00665ca987cd3acae87bc1d988f8ab56b31;p=dbsrgits%2FDBIx-Class.git

diff --git a/lib/DBIx/Class/Relationship.pm b/lib/DBIx/Class/Relationship.pm
index 71c0004..22be1d3 100644
--- a/lib/DBIx/Class/Relationship.pm
+++ b/lib/DBIx/Class/Relationship.pm
@@ -13,23 +13,6 @@ __PACKAGE__->load_own_components(qw/
   Base
 /);
 
-__PACKAGE__->mk_classdata('_relationships', { } );
-
-sub relationships
-{
-    my $self = shift;
-
-    return keys %{$self->_relationships};
-}
-
-sub relationship_info
-{
-    my $self = shift;
-    my ($rel) = @_;
-
-    return $self->_relationships->{$rel};
-}
-
 =head1 NAME 
 
 DBIx::Class::Relationship - Inter-table relationships
@@ -114,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