Greg Willits wrote: [...] > If it just has to be (lots of fields) then it just has to be, but I > would expect that to be rare, and it is not necessary in my current > case. The table contains easily distinguishable topics, and the code > would be better organized, more readable, more orthogonal, simpler to > test, and plain simpler to maintain in smaller pieces along the lines of > the topics I see in this table. [...]
Then yeah, breaking it down probably makes sense. 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.
