From: Mateu X Hunter Date: Sun, 20 Mar 2011 00:20:21 +0000 (-0600) Subject: use relationship bridge consistently w/ many_to_many speak X-Git-Tag: v0.08191~54 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=5947e40961b9814264573afd70326d828a07853a;p=dbsrgits%2FDBIx-Class.git use relationship bridge consistently w/ many_to_many speak --- diff --git a/lib/DBIx/Class/Manual/Cookbook.pod b/lib/DBIx/Class/Manual/Cookbook.pod index d8d5304..014ff38 100644 --- a/lib/DBIx/Class/Manual/Cookbook.pod +++ b/lib/DBIx/Class/Manual/Cookbook.pod @@ -1078,7 +1078,7 @@ If you want to get a filtered result set, you can just add add to $attr as follo __PACKAGE__->has_many('pages' => 'Page', 'book', { where => { scrap => 0 } } ); -=head2 Many-to-many relationships +=head2 Many-to-many relationship bridges This is straightforward using L: diff --git a/lib/DBIx/Class/Manual/FAQ.pod b/lib/DBIx/Class/Manual/FAQ.pod index fa25e22..afcb658 100644 --- a/lib/DBIx/Class/Manual/FAQ.pod +++ b/lib/DBIx/Class/Manual/FAQ.pod @@ -132,9 +132,10 @@ allow you to supply a hashref containing the condition across which the tables are to be joined. The condition may contain as many fields as you like. See L. -=item .. define a relationship across an intermediate table? (many-to-many) +=item .. define a relationship bridge across an intermediate table? (many-to-many) -Read the documentation on L. +The term 'relationship' is used loosely with many_to_many as it is not considered a +relationship in the fullest sense. For more info, read the documentation on L. =item .. stop DBIx::Class from attempting to cascade deletes on my has_many and might_have relationships?