Tim Shaffer wrote in post #1054854: > What problem are you trying to solve by doing this? > > Just seems like it would make your code more complicated with no real > benefit.
DRYer code: this approach has fewer distinct tables, fewer distinct classes, fewer things to test and maintain. But I may be missing something (which is why I'm asking): what part of the code becomes more complicated this with this approach? -- 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.
