Fix $object->search_related aliasing, change semantics of _resolve_condition
authorPeter Rabbitson <ribasushi@cpan.org>
Sun, 16 Jan 2011 00:14:03 +0000 (01:14 +0100)
committerPeter Rabbitson <ribasushi@cpan.org>
Thu, 20 Jan 2011 11:41:16 +0000 (12:41 +0100)
commitaa56106b252283cef5338312d66fdf62cc92df20
tree4b340261c85ee2de58efa20f6d74bae3f5483b6c
parent1605376709663b035385b41828ce13ae3ed45a4d
Fix $object->search_related aliasing, change semantics of _resolve_condition

Change the RV of _resolve_condition one last time. Now it checks the RV of the
resolved coderef (if any), and chooses (preferrably) the join-free condition
or the cross-table one. In list context returns a flag signifying if the
resulting condition is available for standalone use (false) or requires the
joins to remain (true)
lib/DBIx/Class/Relationship/Base.pm
lib/DBIx/Class/Relationship/ManyToMany.pm
lib/DBIx/Class/ResultSource.pm