> Often times it's a performance > necessity, and it's one area where falling back to find_by_sql just > doesn't work because you can't easily construct the association > targets from a raw sql query.
Building a SQL parser immediately sets off all sorts of alarm bells. However perhaps the proper solution is to simply remedy this problem If you can do fancy find_by_sql and get the snippet of your object graph back, then it makes it less important to start guessing intent of our users. The apps I'm working on don't typically need to use complicated queries to return a chunk of the object graph. Most of the hand-written sql I use gets fed into aggregate queries of some kind. If you're currently hitting the limits of the current system, perhaps that's the motivation needed to investigate improving find_by_sql? -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
