[Rails] Re: one master table to hold symbols: good or bad idea?

2012-04-04 Thread Matt Jones
On Tuesday, 3 April 2012 13:32:54 UTC-4, Ruby-Forum.com User wrote: (This is may be more of a db design question than a rails question.) Summary: I'm thinking of creating a single AR class to hold constant symbol values and use it for :has_many_through relations whenever I need a

[Rails] Re: one master table to hold symbols: good or bad idea?

2012-04-03 Thread Tim Shaffer
What problem are you trying to solve by doing this? Just seems like it would make your code more complicated with no real benefit. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Talk group. To view this discussion on the web visit

[Rails] Re: one master table to hold symbols: good or bad idea?

2012-04-03 Thread Fearless Fool
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