Topic: Why the need for more than one model?  Hey everyone,
rails newbie here. One issue I am having trouble wrapping my
head around: Let's say you are building a simple news
application, where users can add comments onto the end of news
submitted by an administrator. If you have an "admin"
controller, which has add, edit and delete functionality for
comments, what need is there for a "user" controller? Can you
not just create "user" displays, and reuse the admin
controller's facilities?   I am working through the "Agile web
development with rails" book, and understand in the shopping
cart scenario how a user and an administrator have different
models and controllres, as users don't do the same action as
admins.  Thanks -  Re: Why the need for more than one model?
Sure you can do that.  You can put everything in one controller
no matter how large your app is.  But why not keep the
functionality separate (and simpler) and use the Rails
conventions as intended?  Rails has one controller for one
model.  This is