Skip to content
Have a legacy database and need some enumerations in your models to match those stupid '4 rows/2 columns' tables with foreign keys and stop doing joins just to fetch a simple description? Or maybe use some integers instead of strings as the code for each value of your enumerations? Here's EnumerateIt..
Pull request Compare This branch is 112 commits behind lucascaton:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


EnumerateIt - Ruby Enumerations

Build Status

Author: Cássio Marques - cassiommc at gmail


Ok, I know there are a lot of different solutions to this problem. But none of them solved my problem, so here's EnumerateIt. I needed to build a Rails application around a legacy database and this database was filled with those small, unchangeable tables used to create foreign key constraints everywhere.

For example:

 Table "public.relationshipstatus"
Column     |     Type      | Modifiers
 code        | character(1)  | not null
 description | character(11) |
  "relationshipstatus_pkey" PRIMARY KEY, btree (code)

select * from relationshipstatus;
code   |  description
1      | Single
2      | Married
3      | Widow
4      | Divorced

And then I had things like a people table with a 'relationship_status' column with a foreign key pointing to the relationshipstatus table.

While this is a good thing from the database normalization perspective, managing this values in my tests was very hard. Doing database joins just to get the description of some value was absurd. And, more than this, referencing them in my code using magic numbers was terrible and meaningless: What does it mean when we say that someone or something is '2'?

Enter EnumerateIt.

About versions compatibility

Versions 1.x.x are NOT backwards compatible with 0.x.x versions. The biggest difference is that on 1.0.0 you need to `extend` the EnumerateIt module inside classes that are going to have enumerated attributes, while in past versions you would use `include`.

Creating enumerations

Enumerations are created as models, but you can put then anywhere in your application. In Rails applications, you can put them inside models/.

class RelationshipStatus < EnumerateIt::Base
    :single   => [1, 'Single'],
    :married  => [2, 'Married'],
    :widow    => [3, 'Widow'],
    :divorced => [4, 'Divorced']

This will create some nice stuff:

  • Each enumeration's value will turn into a constant:

    RelationshipStatus::SINGLE # returns 1
    RelationshipStatus::MARRIED # returns 2 and so on...
  • You can retrieve a list with all the enumeration codes:

    RelationshipStatus.list # [1,2,3,4]
  • You can get an array of options, ready to use with the 'select', 'select_tag', etc family of Rails helpers.

    RelationshipStatus.to_a # [["Divorced", 4],["Married", 2],["Single", 1],["Widow", 3]]
  • You can retrieve a list with values for a group of enumeration constants.

    RelationshipStatus.values_for %w(MARRIED SINGLE) # [2, 1]
  • You can retrieve the value for a specific enumeration constant:

    RelationshipStatus.value_for("MARRIED") # 2
  • You can retrieve the symbol used to declare a specific enumeration value:

    RelationshipStatus.key_for(RelationshioStatus::MARRIED) # :married
  • You can iterate over the list of the enumeration's values:

    RelationshipStatus.each_value { |value| # ... }
  • You can iterate over the list of the enumeration's translations:

    RelationshipStatus.each_translation { |translation| # ... }
  • You can ask for the enumeration's length:

    RelationshipStatus.length # 4
  • You can manipulate the hash used to create the enumeration:

    RelationshipStatus.enumeration # returns the exact hash used to define the enumeration

You can also create enumerations in the following ways:

  • Passing an array of symbols, so that the respective value for each symbol will be the stringified version of the symbol itself:

    class RelationshipStatus < EnumerateIt::Base
      associate_values :married, :single
    RelationshipStatus::MARRIED # returns "married" and so on
  • Passing hashes where the value for each key/pair does not include a translation. In this case, the I18n feature will be used (more on this below):

    class RelationshipStatus < EnumerateIt::Base
      associate_values :married => 1, :single => 2

Using enumerations

The cool part is that you can use these enumerations with any class, be it an ActiveRecord instance or not.

class Person
  extend EnumerateIt
  attr_accessor :relationship_status

  has_enumeration_for :relationship_status, :with => RelationshipStatus

The :with option is not required. If you ommit it, EnumerateIt will try to load an enumeration class based on the camelized attribute name.

This will create:

  • A humanized description for the values of the enumerated attribute:

    p =
    p.relationship_status = RelationshipStatus::DIVORCED
    p.relationship_status_humanize # => 'Divorced'
  • If you don't supply a humanized string to represent an option, EnumerateIt will use a 'humanized' version of the hash's key to humanize the attribute's value:

    class RelationshipStatus < EnumerateIt::Base
        :married => 1,
        :single => 2
    p =
    p.relationship_status = RelationshipStatus::MARRIED
    p.relationship_status_humanize # => 'Married'
  • The associated enumerations can be retrieved with the 'enumerations' class method.

    Person.enumerations[:relationship_status] # => RelationshipStatus
  • If you pass the :create_helpers option as 'true', it will create a helper method for each enumeration option (this option defaults to false):

    class Person < ActiveRecord::Base
      has_enumeration_for :relationship_status, :with => RelationshipStatus, :create_helpers => true
    p =
    p.relationship_status = RelationshipStatus::MARRIED
    p.married? #=> true
    p.divorced? #=> false
  • It's also possible to “namespace” the created helper methods, passing a hash to the :create_helpers option. This can be useful when two or more of the enumerations used share the same constants.

    class Person < ActiveRecord::Base

    has_enumeration_for :relationship_status, :with => RelationshipStatus, :create_helpers => { :prefix => true }


    p = p.relationship_status = RelationshipStatus::MARRIED p.relationship_status_married? #=> true p.relationship_status_divoced? #=> false

  • The :create_helpers also creates some mutator helper methods, that can be used to change the attribute's value.

    class Person < ActiveRecord::Base
      has_enumeration_for :relationship_status, :with => RelationshipStatus, :create_helpers => true
    p =
    p.married? #=> true
    p.divorced? #=> false
  • If you pass the :create_scopes option as 'true', it will create a scope method for each enumeration option (this option defaults to false):

    class Person < ActiveRecord::Base
      has_enumeration_for :relationship_status, :with => RelationshipStatus, :create_scopes => true
    Person.married.to_sql # => SELECT "people".* FROM "people" WHERE "people"."relationship_status" = 1

NOTE: The :create_scopes option can only be used for Rails.version >= 3.0.0.

  • If your class can manage validations and responds to :validates_inclusion_of, it will create this validation:

    class Person < ActiveRecord::Base
      has_enumeration_for :relationship_status, :with => RelationshipStatus
    p = :relationship_status => 6 # => there is no '6' value in the enumeration
    p.valid? # => false
    p.errors[:relationship_status] # => "is not included in the list"
  • If your class can manage validations and responds to :validates_presence_of, you can pass the :required options as true and this validation will be created for you (this option defaults to false):

    class Person < ActiveRecord::Base
      has_enumeration_for :relationship_status, :required => true
    p = :relationship_status => nil
    p.valid? # => false
    p.errors[:relationship_status] # => "can't be blank"

Remember that in Rails 3 you can add validations to any kind of class and not only to those derived from ActiveRecord::Base.


I18n lookup is provided on both '_humanized' and 'Enumeration#to_a' methods, given the hash key is a Symbol. The I18n strings are located on enumerations.'enumeration_name'.'key' :

class RelationshipStatus < EnumerateIt::Base
   :married => 1,
   :single => 2,
   :divorced => [3, 'He's divorced']

# your locale file
      married: Casado

p =
p.relationship_status = RelationshipStatus::MARRIED
p.relationship_status_humanize # => 'Casado'

p.relationship_status = RelationshipStatus::SINGLE
p.relationship_status_humanize # => 'Single' => nonexistent key

p.relationship_status = RelationshipStatus::DIVORCED
p.relationship_status_humanize # => 'He's divorced' => uses the provided string

You can also translate specific values:

RelationshipStatus.t(1) # => 'Casado'


gem install enumerate_it

Using with Rails

  • Create an initializer with the following code:

    ActiveRecord::Base.extend EnumerateIt

  • Add the 'enumerate_it' gem as a dependency in your environment.rb (Rails 2.3.x) or Gemfile (if you're using Bundler)

An interesting approach to use it in Rails apps is to create an app/enumerations folder and add it to your autoload path in config/application.rb:

module YourApp
  class Application < Rails::Application
    config.autoload_paths << "#{Rails.root}/app/enumerations"

There is also a Rails Generator that you can use to generate enumerations and their locale files. Take a look at how to use it running

rails generate enumerate_it --help

Why did you reinvent the wheel?

There are other similar solutions to the problem out there, but I could not find one that worked both with strings and integers as the enumerations' codes. I had both situations in my legacy database.

Why defining enumerations outside the class that use it?

  • I think it's cleaner.

  • You can add behaviour to the enumeration class.

  • You can reuse the enumeration inside other classes.

Note on Patches/Pull Requests

  • Fork the project.

  • Make your feature addition or bug fix.

  • Add tests for it. This is important so I don't break it in a future version unintentionally.

  • Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)

  • Send me a pull request. Bonus points for topic branches.


Copyright © 2010 Cássio Marques. See LICENSE for details.

Something went wrong with that request. Please try again.