Question

I’m working on an ‘analytics’ page for a rails app. The analytics page does not persist any data of its own (it’s very primitive at this point) but does utilize metrics that I’m grabbing from the DB (via the aggregate expressions built into ActiveRecord). Aside from gathering and presenting the metrics the only other requirement I have is to allow the user to provide a date range to filter the data. Up to this point I have been using instance variables and the like to store the metrics information…as the number of metrics grow along with the need to manage the start and end filter dates I begin thinking that I should put this data into its own model. If I do move all of my ‘data’ into a model should I just use a plain object with attr_accessors or is there a more appropriate base class I could use for non-persistent data? I’m familiar enough with a MVC architecture to know that my controller is getting to bloated but no familiar enough with rails to determine how I should organize my data/logic in this case.

Any insight would be greatly appreciated!

Answer 1

It sounds like you could use a Rails non active-record model. There’s a good Railscast about that :

http://railscasts.com/episodes/121-non-active-record-model

Hope that helps,