You want the controller to responsible for passing model data from the database to the view and vice versa. You don't want to clutter the controller with model specific logic...that's why you want it in the model where it's self-contained. Try this article:
http://www.therailsway.com/2007/6/1/railsconf-recap-skinny-controllers On Sep 3, 2:09 pm, Aldric Giacomoni <rails-mailing-l...@andreas-s.net> wrote: > I've read this a few times recently. > I thought a model's job was only to explain "This is how I behave > myself" and the controller's job was to explain "This is what I do". > Is this basically right? So why do people want to stuff more and more > stuff in the model? > -- > Posted viahttp://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 rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
