Maybe not directly relevant, but have you considered that you may have normalized your database into nonfunctionality? From the queries you've shown, most of the tables have one data field(?!), a date, and a foreign key field for the team. This would be an appropriate structure for describing a system where each type of statistic might be generated at different times, but it seems completely inappropriate for your application where all the stats are (obviously) generated simultaneously.
Why did you decide to go this way, vs a single 'stats' table for everything? --Matt Jones --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
