From: Peter Rabbitson <ribasushi@cpan.org>
Date: Wed, 20 Feb 2013 11:05:31 +0000 (+0100)
Subject: Clarify prefetch documentation a bit, remove the nonsensical 0.09 warning
X-Git-Tag: v0.08241~1
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=9f30030205481d5b2c8d0f7d637259c5ae6dd52d;p=dbsrgits%2FDBIx-Class.git

Clarify prefetch documentation a bit, remove the nonsensical 0.09 warning
---

diff --git a/lib/DBIx/Class/ResultSet.pm b/lib/DBIx/Class/ResultSet.pm
index c944b45..5dc6454 100644
--- a/lib/DBIx/Class/ResultSet.pm
+++ b/lib/DBIx/Class/ResultSet.pm
@@ -4552,8 +4552,11 @@ traversing a relationship. So, if you have C<< Artist->has_many(CDs) >> and you
 
   cmp_ok( $count, '==', $prefetch_count, "Counts should be the same" );
 
-That cmp_ok() may or may not pass depending on the datasets involved. This
-behavior may or may not survive the 0.09 transition.
+That cmp_ok() may or may not pass depending on the datasets involved. In other
+words the C<WHERE> condition would apply to the entire dataset, just like
+it would in regular SQL. If you want to add a condition only to the "right side"
+of a C<LEFT JOIN> - consider declaring and using a L<relationship with a custom
+condition|DBIx::Class::Relationship::Base/condition>
 
 =back