from being switched to foobar. For example, if I have a class with many LolCats, if I try to call lolcats on an instance it would give a nomethod error, since I should be calling lol_cats.
The existing code would break on associations that did not fall into a 'simple' naming convention. AAR would break if the name model class name could not be derived from the association name, for example: has_many :biases, :class_name => "Bias" Since ActiveRecord provides reflection capabilities on the association, I just leveraged those so AAR doesn't have to.
* Add limit option * Add option to split dataset