Tony wrote: > I guess no one else has run into this or seen it as a problem? > > tony
I had users who wanted something similar. I ended up creating views in the DB (MySQL), controllers and models for those views, which let the DB do all the ugly join and aggregate work, and gave me, effectively, read-only models to populate 'index' forms. I later added in 'index row' fragment caching for those views, so even the DB is hit less and less. -- 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
