Is there a historical reason why #transaction is defined as both an
instance and class method within ActiveRecord models? I bring this up
specifically because it prevents us from using "transaction" as an
association name like so:
class PaymentTransaction < ActiveRecord::Base
class PaymentAccount < ActiveRecord::Base
has_one :transaction, :class_name => 'PaymentTransaction'
This obviously won't work because the #transaction instance method is
used throughout ActiveRecord::Transactions instead of the class
Does anyone have any thoughts on solely using the class method to
avoid a common name collision like this?