By "avoid supplementing the database end of things", I mean I want to avoid adding more tables or databases to the database engine, inserting an additional database layer.
Yes, I'm currently intending to "munge" the unorganized fields into a string, and deal with the parsing/processing at another stage. yes, it's inefficient, but it's a relatively small amount of processing, and hopefully it will get me to where I need to be within a short amount of time, which is a factor in this situation. By "not preserving record integrity", I mean that I am not updating any of these records, it's read-only. I want to pull the data and generate reports, both for screen and CSV stream. Yes, most of the processing would be in the Model, not the Controller, but since the model is not a good representation of the existing database schema, there's going to be some fudging going on. The question is whether it's worth bothering to model the final data output at all. I know that helpers are for presentation formatting, which is why I specified that the helper process would be for the "screen". Thanks. On Oct 6, 10:35 am, Marnen Laibow-Koser <[email protected]> wrote: > 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-Koserhttp://www.marnen.org > [email protected] > > -- > Posted viahttp://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.
