chewmanfoo wrote: > what Scott was asking for originally was a way to enumerate options > without having to reference their position in a list. if you use a > database to create the list, then you necessarily have to reference > their position get to them, but if you define the list with, say, a > yml file, then position is irrelevant. So, you can alter the list at > will without having to worry about the consequences for objects which > reference the list - you just can't delete an item in the list.
Nope, wrong. Primary key is not "position in a list". Please learn a bit more about how SQL databases actually work. 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.
