Well I found a way to reach a middle ground. I created a cache table that houses the exact fields for the data I pull using VM. So, the methods that pull the data were moved to a task and I can pre-populate the cache table with the data for that week.
So, my cache table will have 120 rows and 67 fields of data for each week. When people use the VM matchups, they are only querying that table so one table, no joins etc., and it's a lot smaller than 500+ fields. -- 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 -~----------~----~----~----~------~----~------~--~---
