Please quote when replying; otherwise, the discussion becomes difficult to follow.
jrq wrote: > Good and reasonable suggestions. I'd rather avoid supplementing the > database end of things. I'm not sure what you mean by this. Basically, if you're going to use Rails, you have to make sure that it and the DB understand each other. > The complete data set is fairly small <20,000 > rows and queries are likely to only return 1,000 rows at a time. I > don't think the string parsing is <i>that</i> complex, a couple of > seconds would be OK, 10 seconds, not so much. 3 But you'd be munging all the fields together in the query, then separating them in the app. That's a lot of unnecessary string processing. It would be better to avoid ti. > It's for read-only > reports, so I don't really care about preserving the record integrity. Huh? > I'm wondering whether it makes sense to do half the processing in the > controller/model, Controllers shouldn't do processing. > and half in some helper (for the screen aspect). Unlikely. Dealing with the DB is really the job of the model. Helpers are only for presentation formatting. 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.
