I recommend keeping the table. Let me explain why and try to explain
how to set it up better.
This type of information is known at the outset of the application and
it sounds like it is unlikely to change significantly over time. As
such it could be pulled into a domain table, similar to states
Hi
Thanks for all your help
Tom
--
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 rubyonrails-t...@googlegroups.com.
To unsubscribe from this group, send
2 matches
Mail list logo
