I've had a couple of instances where I've wanted to work with an attribute in
an ActiveRecord through another class. For example I'm storing time zones in
my database as strings, but I want to always deal with them through a
TimeZone object. Same goes for time intervals.
I've been using aggregati
> > At a slight tangent, isolating application sessions won't fully solve
> > this problem; you can change the name of a Model object and see this
> > 'white screen of death' within the same application. Something needs
> > to be wrapped around the session loading to let Rails gracefully
> > handl
