+1 Rails has usually been about clean queries over performant ones. :include came way after associations, for example, but :include solved a real problem visible in real applications.
No benchmarking makes sense outside the context of a real application, and this patch would benefit real applcations which can then determine whether there is a painful spot that needs work. In other words this would help most people most of the time who have run into this rather common situation and have solved it in ways that would be equally performant without making specific optimizations like splitting into multiple queries. Josh --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
