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.
On May 18, 10:35 am, Michael Pavling <[email protected]> wrote: > On 18 May 2010 16:28, chewmanfoo <[email protected]> wrote: > > > then your objects which reference them are all re- > > categorized. that's bad - it's a dependency that is unnecessary. > > ?? > > Only if the "somehow" you re-order them by is to change the content of > the object because you assume "id" is "position". > > -- > 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 > athttp://groups.google.com/group/rubyonrails-talk?hl=en. -- 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.
