Rails Model, View, Controller, and Helper: what goes where?

Question

In Ruby on Rails Development (or MVC in general), what quick rule should I follow as to where to put logic.

Please answer in the affirmative - With Do put this h

Answer 1

Perfect explanations here already, one very simple sentence as conclusion and easy to remember:

We need SMART Models, THIN Controllers, and DUMB Views.

http://c2.com/cgi/wiki?ModelViewController

Answer 2

The Rails way is to have skinny controllers and fat models.

Answer 3

In simple terms, generally, Models will have all the codes related to table(s), their simple or complex relationships (think them as sql queries involving multiple tables), manipulation of the data/variables to arrive at a result using the business logic.

Controllers will have code/pointers towards the relevant models for the job requested.

Views will accept the user input/interaction and display the resultant response.

Any major deviation from these will put unwanted strain on that part and the overall application performance may get impacted.

Answer 4

Well, it sort of depends upon what the logic has to deal with...

Often, it makes sense to push more things into your models, leaving controllers small. This ensures that this logic can easily be used from anywhere you need to access the data that your model represents. Views should contain almost no logic. So really, in general, you should strive to make it so that you Don't Repeat Yourself.

Also, a quick bit of google reveals a few more concrete examples of what goes where.

Model: validation requirements, data relationships, create methods, update methods, destroy methods, find methods (note that you should have not only the generic versions of these methods, but if there is something you are doing a lot, like finding people with red hair by last name, then you should extract that logic so that all you have to do is call the find_redH_by_name("smith") or something like that)

View: This should be all about formatting of data, not the processing of data.

Controller: This is where data processing goes. From the internet: "The controller’s purpose is to respond to the action requested by the user, take any parameters the user has set, process the data, interact with the model, and then pass the requested data, in final form, off to the view."

Hope that helps.