Rick, :after_find doesn't exist by default. It only gets called if it is defined. The way I set this up, it defines an 'after_find' callback in ActiveRecord::Base, so other plugins or classes would have to alias the one I defined to get it to work right.
I'm tinkering around with some methods to avoid this completely, but I wanted to get something testable out there for people to play with first. _Kevin On Sunday, February 19, 2006, at 3:47 PM, Rick Bradley wrote: >Kevin, >Thanks for the good work putting this together. > >> There are some important limitations to note. Most importantly, >>it uses >> the ActiveRecord after_find callback. This means that if you are using >> this callback already, you will need to call super in your callback >> routine somewhere or it will not run at all. > >Quick question: why not alias the original :after_find so it can be >chained? > >Rick >-- > http://www.rickbradley.com MUPRN: 422 > | know that you're a > random email haiku | target, you should filter your > | power thoroughly. >_______________________________________________ >Rails-core mailing list >[email protected] >http://lists.rubyonrails.org/mailman/listinfo/rails-core -- Posted with http://DevLists.com. Sign up and save your time! _______________________________________________ Rails-core mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-core
