Hi, using a counter cache would be the most efficient because there's no query. After you set it up, you'll do the following:
ticket.issues.size Good luck, -Conrad Sent from my iPhone On Sep 16, 2008, at 8:45 PM, surge <[EMAIL PROTECTED]> wrote: > > Well, I'm trying to go the easy route first -- using eager loading. > > Interestingly enough, when I added ":issues" to :include, the query > was correctly modified by rails to include a left join with issues. My > expectation now was that when I did ticket.issues.count, no additional > "count" query would be needed. But nope, Rails still does it. > > I kind of don't want to deal with a cache counter or :joins... I would > like to ride the automation wave as long as possible... > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
