Peter Bell wrote in post #974422: > It probably is, but why were you putting the data into a database? If > there's a valid reason to do that, do it and then fix db performance > with caching if it becomes a limiting factor. > > If there's not a valid reason to put the data into a database, why would > you do so? Start with the simplest thing that would possibly work to get > your tests passing and go from there. [...]
With Rails, sometimes using a DB is the simplest thing, and it's actually harder not to do so. But I agree with the sentiment. 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]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
