Frederick Cheung wrote: > On May 10, 8:24�pm, Andrew Selder <[email protected]> > wrote: > >> One option would be into use nested includes to include the payers; but >> this has some serious performance issues. The ticket sets table is large >> and we don't need to the payers data returned, just for selection. >> >> Does anybody have any ideas? >> > it looks like a bug in the code that determines which include strategy > should be used > > Fred
Fred, Do you want me to file a bug at lighthouse? Thanks, Andrew -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
