Thanks a lot Chris. Sadly, I've got my work cut out for me, as changing the name of the model in this fairly mature application is going to be some work. But at least it all makes some sense now.
Is it possible to change the model name without changing the name of the _associations_ that point to it in other models? Or, I guess, to alias the association name 'request' to an 'actual' association named service_request or whatever. To give me less code that has to be changed? Any advice as to the lowest impact way to change a model name in a mature application with lots of code that refers to that model, and to associations in other models that point to that model? Odd that I got away with it in Rails 1.x, but oh well, I guess it was really incorrect all along. Jonathan Chris Bartlett wrote: > Jonathan is probably right. 'Request' is a reserved word in Rails - > see http://wiki.rubyonrails.org/rails/pages/ReservedWords > > Try changing the model name to ServiceRequest or similar. > > On Nov 7, 6:43�am, Jonathan Rochkind <[EMAIL PROTECTED] -- 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 rubyonrails-talk@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
