create now on resultset as well

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

diff --git a/lib/DBIx/Class/Relationship.pm b/lib/DBIx/Class/Relationship.pm
index 15f1bc6..3a68ee2 100644 (file)
--- a/lib/DBIx/Class/Relationship.pm
+++ b/lib/DBIx/Class/Relationship.pm
@@ -6,9 +6,7 @@ use warnings;
 use base qw/DBIx::Class/;
 
 __PACKAGE__->load_own_components(qw/
-  HasMany
-  HasOne
-  BelongsTo
+  Helpers
   Accessor
   CascadeActions
   ProxyMethods
@@ -100,6 +98,12 @@ except the implication is that the other object is always present. The only diff
 between C<has_one> and C<might_have> is that C<has_one> uses an (ordinary) inner join,
 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;                                            
+
 =cut
 
 1;