Michael Pavling wrote: > > Overloading method_missing is probable to cause more problems than it > fixes :-)
I know - it is a very VERY temporary solution to get peace to do real fixing. :-) > You only need to fix the missing associations one at a time; get a > MissingUser in there and all the nil users will disappear. Then if you > discover another nil association, create the MissingModel for that. Yup it is a very neat solution, that I will adapt to. Thanks - Carsten -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en.
