NoMethodError in AssociationProxy#method_missing isn't helpful

Raising NoMethodError directly in AssociationProxy's method_missing call is not a good idea. If the target object has its own method_missing call to implement some functionalities, it never called when it used in an association.

Perhaps it's better just to call the superclass?

@@ -206,7 +209,7 @@ module ActiveRecord
         # Forwards any missing method call to the \target.
         def method_missing(method, *args)
           if load_target
-            raise NoMethodError unless @target.respond_to?(method)
+            super unless @target.respond_to?(method)

I don't think this was resolved correctly. association proxies should pass the method call on to the target so that the target can deal with it in its own method_missing, otherwise you're crippling a lot of meta-programming on AR objects

Perhaps the target could be sent the method inside a begin..rescue block that catches a NoMethodError and gives a more descriptive error, that way the AR object still has a chance to respond.

I have a better solution, which I've provided with a patch in #2378 AssociationProxy#method_missing masks method_missing in models