Good practice

[eluser]moodh[/eluser]
[quote author="shadow player" date="1310398082"]

can you post a link to that thread? I’d be interesting in reading their reasons for that

http://chat.stackoverflow.com/transcript...893#985893

Lets say you want to validate user input but not admin input, through the same model?

Admin input has to be validated too. Stuff admins can input and users can't (i.e. HTML in a post) are commonly set on a permission level.
If an admin accesses a common routine in a model (i.e. creating an user) that would 'normally' be accessed on user registration - he still has to enter a valid email address for the user.[/quote]

What if there's different rule sets for admins and users? Should you create a massive model instead of 2 thin controllers? That just seems well.. Weird.

Models should have a clean interface towards the database. What if you build a script to use a model that really doesn't need any validation? Then you'd have tons of validation in the way. Validation is only needed for user input, there's nothing saying your models wont be used by the system itself in various situations.