2009 April 16
Transparent Access to a Serialized Column in ActiveRecordI started a job a few weeks ago where we're using Ruby on Rails. I had never used it before, and am starting to learn why it has been able to grow as quickly as it has -- it's just damn cool in a lot of ways.
One technique we used a lot in my previous company was to allocate a column in a database to be a "catch-all" for various attributes, in the form of a serialized hash. The advantage here is that if we want to add an attribute to a table, we would not need to alter the table unless we absolutely had to in order to facilitate SELECTs or ORDERing. When we'd read a row from the table, we would de-serialize that column and make that hash available to whatever uses it.
Ruby on Rails' ActiveRecord class handles this seamlessly. Just tell your model to serialize the column like so:
class MyModelClass < ActiveRecord::Base serialize :data enddata is the name of the column that holds the serialized data.
If you want to enforce the type of data that can be serialized/deserialized, add the type name:
class MyModelClass < ActiveRecord::Base serialize :data, MyDataClass end
You can then call methods on the object represented in the data column by referencing it like this:
row = MyModelClass.find :first row.data.foobarassuming MyDataClass implements a method called foobar.
So far so good right? Well, let's say MyDataClass implements a nice object-model of a hash, so calling MyDataClass#keyname will return the value referenced by the key. You write a bunch of views referencing row.data.foobar or row.data.snafu, but at a later date you decide that you really want to dedicate a column in the database table to the value held by data.foobar. So you have to visit all your views to be sure you make the change from row.data.foobar to row.foobar. Crappy!
Wouldn't it be nice to just design it from the start so that you could call row.foobar? That way, it's at the model's discretion whether a bit of data is stored in the serialized column or a "real" column. Nice, right?
Well, it's pretty easy to do. We'll define a Mix-In that we'll load into certain model classes. This mix-in will override the method_missing and respond_to? methods of the class with our own design.
Here is the content of lib/model_data_column.rb:
## # Model Data Column Mix-In # Include this in your data model if you use 'data' as a serialized object. # This will let you call "model.foo" rather than "model.data.foo" # to facilitate moving data between the serialized 'data' column # and real DB columns. module ModelDataColumn
def method_missing(method_id, *args) self[:data].send(method_id, args) || super end
def respond_to?(method_id, *args) self[:data].send(:respond_to?, method_id) || self[:data].send(:has_key?, method_id.id2name) || super end
Note: the class behind your serialized column (MyDataClass in this case) needs to implement the method has_key?.
Use it in your model like this:
class MyModelClass < ActiveRecord::Base include ModelDataColumn serialize :data, MyDataClass end
So now you can call methods in your serialized object column without explicitly referencing the column! This means the rest of your application does not need to concern itself with how the model has implemented the storage of the data. It will just work.
There is a danger if the serialized column holds a value with the same key as the name of a database column. The model will always return the value from the DB column in this case. However, the benefits of this model are big enough for us where we will trade that for the need to keep tabs on the names of things we are storing.
So now this old code:
row = MyModelClass.find :first row.data.foobarAnd this new code:
row = MyModelClass.find :first row.foobarWill have the same output. Huzzah!