Skip to content
Object-Hash Mapping for Redis
Pull request Compare This branch is 715 commits behind soveran:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Ohm ॐ

Object-hash mapping library for Redis.


Ohm is a library for storing objects in Redis, a persistent key-value database. It includes an extensible list of validations and has very good performance.

Getting started

Install Redis. On most platforms it's as easy as grabbing the sources, running make and then putting the redis-server binary in the PATH.

Once you have it installed, you can execute redis-server and it will run on localhost:6379 by default. Check the redis.conf file that comes with the sources if you want to change some settings.

If you don't have Ohm, try this:

$ sudo gem install ohm

Or you can grab the code from

Now, in an irb session you can test the Redis adapter directly:

>> require "ohm"
=> true
>> Ohm.connect
=> []
>> Ohm.redis.set "Foo", "Bar"
=> "OK"
>> Ohm.redis.get "Foo"
=> "Bar"


Ohm's purpose in life is to map objects to a key value datastore. It doesn't need migrations or external schema definitions. Take a look at the example below:


class Event < Ohm::Model
  attribute :name
  set :participants
  list :comments
  counter :votes

  index :name

  def validate
    assert_present :name

All models have the id attribute built in, you don't need to declare it.

This is how you interact with ids:

event = Event.create :name => "Ohm Worldwide Conference 2031"
# => 1

# Find an event by id
event == Event[1]
# => true

# Trying to find a non existent event
# => nil

This example shows some basic features, like attribute declarations and validations. Keep reading to find out what you can do with models.

Attribute types

Ohm::Model provides four attribute types: attribute, set, list and counter.


An attribute is just any value that can be stored as a string. In the example above, we used this field to store the Event's name. You can use it to store numbers, but be aware that Redis will return a string when you retrieve the value.


A set in Redis is an unordered list, with an external behavior similar to that of Ruby arrays, but optimized for faster membership lookups. It's used internaly by Ohm to keep track of the instances of each model and for generating and maintaining indexes.


A list is like an array in Ruby. It's perfectly suited for queues and for keeping elements in order.


A counter is like a regular attribute, but the direct manipulation of the value is not allowed. You can retrieve, increase or decrease the value, but you can not assign it. In the example above, we used a counter attribute for tracking votes. As the incr and decr operations are atomic, you can rest assured a vote won't be counted twice.


Ohm lets you use collections (lists and sets) to represent associations. For this, you only need to provide a second paramenter when declaring a list or a set:

set :attendees, Person

After this, everytime you refer to event.attendees you will be talking about instances of the model Person. If you want to get the raw values of the set, you can use event.attendees.raw.

The attendees collection also exposes two sorting methods: sort returns the elements ordered by id, and sort_by receives a parameter with an attribute name, which will determine the sorting order. Both methods receive an options hash which is explained in the documentation for {Ohm::Attributes::Collection#sort}.


An index is a set that's handled automatically by Ohm. For any index declared, Ohm maintains different sets of objects ids for quick lookups.

For example, in the example above, the index on the name attribute will allow for searches like Event.find(:name, "some value").

Note that the find method and the assert_unique validation need a corresponding index to exist.


Before every save, the validate method is called by Ohm. In the method definition you can use assertions that will determine if the attributes are valid. Nesting assertions is a good practice, and you are also encouraged to create your own assertions. You can trigger validations at any point by calling valid? on a model instance.


Ohm ships with some basic assertions. Check Ohm::Validations to see the method definitions.


The assert method is used by all the other assertions. It pushes the second parameter to the list of errors if the first parameter evaluates to false.

def assert(value, error)
  value or errors.push(error) && false


Checks that the given field is not nil or empty. The error code for this assertion is :not_present.

def assert_present(att, error = [att, :not_present])
  assert(!send(att).to_s.empty?, error)


Checks that the given field matches the provided format. The error code for this assertion is :format.

def assert_format(att, format, error = [att, :format])
  if assert_present(att, error)
    assert(send(att).to_s.match(format), error)


Checks that the given field holds a number as a Fixnum or as a string representation. The error code for this assertion is :not_numeric.

def assert_numeric(att, error = [att, :not_numeric])
  if assert_present(att, error)
    assert_format(att, /^\d+$/, error)


Validates that the attribute or array of attributes are unique. For this, an index of the same kind must exist. The error code is :not_unique.

def assert_unique(attrs)
  result = db.sinter(*Array(attrs).map { |att| index_key_for(att, send(att)) })
  assert(result.empty? || result.include?(id.to_s), [attrs, :not_unique])


When an assertion fails, the error report is added to the errors array. Each error report contains two elements: the field where the assertion was issued and the error code.

Validation example

Given the following example:

def validate
  assert_present :foo
  assert_numeric :bar
  assert_format :baz, /^\d{2}$/
  assert_unique :qux

If all the assertions fail, the following errors will be present:

# => [[:foo, :not_present], [:bar, :not_numeric], [:baz, :format], [[:qux], :not_unique]]

Note that the error for assert_unique wraps the field in an array. The purpose for this is to standardize the format for both single and multicolumn indexes.

Presenting errors

Unlike other ORMs, that define the full error messages in the model itself, Ohm encourages you to define the error messages outside. If you are using Ohm in the context of a web framework, the views are the proper place to write the error messages.

Ohm provides a presenter that helps you in this quest. The basic usage is as follows:

error_messages = @model.errors.present do |e|
  e.on [:name, :not_present], "Name must be present"
  e.on [:account, :not_present], "You must supply an account"

# => ["Name must be present", "You must supply an account"]

Having the error message definitions in the views means you can use any sort of helpers. You can also use blocks instead of strings for the values. The result of the block is used as the error message:

error_messages = @model.errors.present do |e|
  e.on [:email, :not_unique] do
    "The email #{} is already registered."

# => ["The email is already registered."]
Something went wrong with that request. Please try again.