Fixed set of values for an attribute and migrations


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
The second, two strings: building or garage.
The correct way of doing this is restricting to this values in the
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
Hope I explained myself properly.


Check out validates_inclusion_of

On Feb 3, 9:10 am, Juan K. removed_email_address@domain.invalid