The most jarring example of this is that validates_uniqueness_of ... doesn't.
I'm looking into access control solutions, and came again across the Ruby on Rails Security Cheat Sheet.
So... my layoff from Touchtunes finally happened. And three weeks later I chose an offer from Zenoss (http://www.zenoss.com) over AMD (http://www.amd.com).
Maybe I'm the only one to waste a lot of time chasing this down, but...
x = method(parm) rescue nil
Rails has *ahem* a lot of methods available to ActiveRecord::Base descendant class objects, and we are warned not to use these as column names.
Suppose you have a model with two associations. Both attach to the same table. Both have conditions. Suppose you want to load both at the same time. You may have a problem.
Two things to be aware of here:
Ruby on Rails tries to be efficient (and there is much rejoicing). One of the tricks that is uses is to optimize ActiveRecord::Base#save.
Ruby on Rails is (deservedly) a popular and growing web development framework. It has its problem, those can be fixed.
Six months of looking after AMD's big ax hit, and I'm back to work.
