On 2 December 2010 20:48, Cameron Caine <[email protected]> wrote: > Tom Tom wrote in post #965788: >> cameron, maybe u can throw in a kinda of a team-statistics table which >> holds >> all the aggregated values? and update / insert them once u enter the >> results >> of a game... >> not always 3rd-DB-Form, but often preferrable. >> regards tom > > The problem is that the team stats will be calculated based on different > date ranges and therefore I can't really cache a specific set. The > individual game stats might be more feasible.
I would advise against storing calculated values in the database at the start. It adds complexity to the code and subtle bugs can be introduced that may not be seen immediately. If performance becomes an issue at some point in the future then that is the time to do it. Though even then it may not be the best way to improve performance. Bottlenecks in apps are rarely at the points that were imagined at the design stage. Colin -- 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.
