+1 based on a cursory glance The only reason to reject this would be that the algorithm is flawed. The fact that it produces a complex query should not be an issue. By and large you WANT these kinds of things to be taken care of by the database where indexes and other optimizations are more efficiently brought to bear. If you need this kind of logic, there's no getting around the irreducible complexity. Let's have ActiveRecord do its best for the general case, and let application writers take care of the hacky optimizations for individual cases.
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
