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
On Thu, Dec 2, 2010 at 3:36 PM, Marnen Laibow-Koser <[email protected]>wrote: > Please avoid top-posting. > > Cameron Caine wrote in post #965778: > > Thanks this certainly helps. Any reason in particular why you don't > > recommend getting aggregates in the same query? > > I thought about that again after I posted it. It's less easy to use > ActiveRecord's abstraction layer, and you may be getting a lot of data > you don't need if you pack everything into the one query. But it's > probably not as inadvisable as I had originally implied. > > > > > Things I need so far as is results like: > > > > Win Count > > Loss Count > > Draw Count > > Win % > > Home Wins % > > Away Wins % > > Scoring Average > > Yes? And how are these calculated? > > > > > The list goes on and on and into nested models in the game: > > Best, > -- > Marnen Laibow-Koser > http://www.marnen.org > [email protected] > > -- > 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]<rubyonrails-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- 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.
