On 18 January 2011 18:56, Simon M. <[email protected]> wrote: > > Hi thanks for the response, ah,your right because i had to create the > model, view, controller as register_user instead of user(which was how > it was done from a tutorial!, I copied the code form that same tutorial) > > it just that i get aload error message when i change it to RegisterUser > and a name error message when i then tried register_user as well > > > > So i have to change user ro RegisterUser everywhere in the controller > views etc?
That depends on what you are doing. You should have a model and table that agree with each other (User and users or RegisterUser and register_users). RegisterUsers sounds a strange name for a model and table though. Usually a table maps to something in the real world (such as users). If you have a table called register_users then does each row represent a RegisterUser (whatever that is)? There need not be a controller with the same name however, so I am guessing that maybe the controller should be called register_users as that is what it does. Only you know what your app is supposed to be doing though. Colin -- 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.
