Check out validates_inclusion_of http://api.rubyonrails.org/classes/ActiveRecord/Validations/ClassMethods.html#M002112
On Feb 3, 9:10 am, Juan Kinunt <rails-mailing-l...@andreas-s.net> wrote: > Hi, > I have a model with three attributes that could be a fixed set of > different values. Each attribute does not have sufficient entity to be a > class (in my opinion) and I prefer to not to create classes in order to > store them. > For example, one attribute can be only three strings: phone, email or > fax. > The second, two strings: building or garage. > The correct way of doing this is restricting to this values in the > model? > Is there something I can/have to do in the migration? > I'm thinking about a validation of each field in the model and a > selection-option field in the forms. Is this the best pattern in order > to implement this? Would you prefer to create models for each of this > attributes? > Hope I explained myself properly. > Thanks. > -- > Posted viahttp://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-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
