Put another way, when business rules change, you change your models. When business behavior changes, you change your controllers.
Put another way, when business rules change, you change your models. When business behavior changes, you change your controllers.
Your actual procedural stuff that's actually deciding what to do to and with the data doesn't go in the database (stored proc fanboys be damned), and likewise doesn't go in the model.
If you add such rules in the controller, you have to split your rules in two places, which is bad.
Ideally, I always thought that business rules should be a kind of "config", or more accurately a set of files written in a mini-domain language, that would be readable by PMs. Then it would be the job of the model to interface this set of rules with the controller.
So no, business rules and logic and whatever do not belong to the controller.
Yes, 100% absolutely, no question.
>That fits into the class of behavior and belongs in a controller.
The controller is just to handle input, it has nothing to do with behavior. This is one of the key misunderstandings that differentiates between MVC and the weird mess rails calls MVC.
It has a very specific meaning: http://en.wikipedia.org/wiki/Model–view–controller
>At the same time, I also don't think such a rule belongs in your model layer.
I'm not talking personal preference, I am talking how MVC works. If your application were MVC, then yes it absolutely would be in the model.