On Feb 19, 8:18 pm, "Michael B." <[email protected]> wrote:
> The two questions I have are:
>
> 1) Why AR is paying attention to what's in the ORDER parameter and
> choosing the eager loading strategy based from that?
Mainly for backwards compatibility AR falls back to the join based
include stuff when it thinks you're referencing (in conditions, order
etc..) something from one of the included tables, because clearly
having a condition on a table you don't join won't work. In 2.2 it's
not smart enough to scan the joins clause to see that references to
those tables are OK (it is in rails 2.3).
> 2) Is there any way I can force AR to choose the loading strategy? Or
> at least tell it not to do a LEFT OUTER JOIN.
Not that I know of
Fred
>
> -- Michael
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
