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 end class PaymentAccount < ActiveRecord::Base has_one :transaction, :class_name => 'PaymentTransaction' end This obviously won't work because the #transaction instance method is used throughout ActiveRecord::Transactions instead of the class method. Does anyone have any thoughts on solely using the class method to avoid a common name collision like this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
