From: Alessandro Ranellucci Date: Sat, 7 Apr 2012 17:37:33 +0000 (+0200) Subject: Mention the internal join pruner in POD X-Git-Tag: v0.08204~14 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=c3de6b51c8616162e22e8be6e57a2f4d6306b969;p=dbsrgits%2FDBIx-Class.git Mention the internal join pruner in POD --- diff --git a/lib/DBIx/Class.pm b/lib/DBIx/Class.pm index aa79715..f4d573c 100644 --- a/lib/DBIx/Class.pm +++ b/lib/DBIx/Class.pm @@ -283,6 +283,8 @@ aherzog: Adam Herzog Alexander Keusch +alexrj: Alessandro Ranellucci + alnewkirk: Al Newkirk amiri: Amiri Barksdale diff --git a/lib/DBIx/Class/ResultSet.pm b/lib/DBIx/Class/ResultSet.pm index 3e629ec..eb6e7d7 100644 --- a/lib/DBIx/Class/ResultSet.pm +++ b/lib/DBIx/Class/ResultSet.pm @@ -3999,6 +3999,12 @@ to Earth' and a cd with title 'Popular'. If you want to fetch related objects from other tables as well, see C below. + NOTE: An internal join-chain pruner will discard certain joins while + constructing the actual SQL query, as long as the joins in question do not + affect the retrieved result. This for example includes 1:1 left joins + that are not part of the restriction specification (WHERE/HAVING) nor are + a part of the query selection. + For more help on using joins with search, see L. =head2 prefetch