Do not artificially order the internals of a has_many prefetch subquery
authorPeter Rabbitson <ribasushi@cpan.org>
Sat, 21 Apr 2012 04:03:34 +0000 (06:03 +0200)
committerPeter Rabbitson <ribasushi@cpan.org>
Sat, 21 Apr 2012 04:03:34 +0000 (06:03 +0200)
commit946f626022c63fd269d9d985c2abeabb52871027
tree3e05b8d07174662cf551e0fd151ce10f3c05a2ee
parent13fa2937f8b3299a135f8c8878915098b2d8456c
Do not artificially order the internals of a has_many prefetch subquery

Thre is no point using the artificial order which is only needed for efficient
collapse. The user didn't request an order - this means any rows will do
lib/DBIx/Class/ResultSet.pm
lib/DBIx/Class/Storage/DBIHacks.pm
t/prefetch/grouped.t
t/prefetch/with_limit.t