Actually this naming problem is one of the hard-to-bite problems that hit everyone new and old to Ruby. We were recently hit by another couple of those name clashes: turns out you can not name your model attribute "binding" (this was appropriate for the model "Book"), nor can you use an attribute called "target" in your model. The unfortunate name collision problem is very hard to detect. The binding attribute/method was conflicting with Proc.binding and throwing error deep down ActiveRecord stack. If anyone knows a good approach to resolving name conflicts, or at least testing whether an issue being diagnosed may be a result of a name clash, please share. Thanks Konstantin On Sep 6, 2006, at 1:24 PM, Zed Shaw wrote:
|
_______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
