Taylor Strait wrote: > Kristian - thanks for the reply. I think it would be easier, too! But... > I was wondering if I am violating some kind of best practice to put all > the fields in one model even if half of them will be empty most of the > time?
i think it can sometimes be a fault to over-engineer a solution beyond the 'fit for purpose' threshold ;) A textbook solution may be option B and i think it looks the more interesting challenge but in reality you know your system best. If option A is the best fit (and consider your longer term plans as well here) then why not. -- 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.
