On Jul 14, 2007, at 11:13 AM, Bernardo de Pádua wrote:
> I also think this kind of nesting is the logical > thing to support, as I've seen many users think (myself included) that > it was already there in Rails, try it and be surprised with the errors > it caused. If the Rails way was wanting the user to do custom > "optimized" queries all the time, perhaps it shouldn't even have > associations or finders. > This is the most important point to make. If you all remember, nested includes was merged into core because of its elegant implementation and the obvious logical fit of the behavior. http://dev.rubyonrails.org/ticket/3913 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 -~----------~----~----~----~------~----~------~--~---
