[eluser]Twisted1919[/eluser]
Well , models are useful when you do repetitive tasks in distinct places .
Personally , i just don't like to see any sql code into my controllers ... without that , i have a cleaner code , i guess i've just like this way , so it's all about organization.
For instance , having an app that display the username on every page , would require you to write sql queries for each of your controllers right ?
Why do that ? when you can create a model , place a function that retrieve the username , then from your controllers just call that function .
Later on , you will decide you want to show he's last login , if you hadn't used models , you would need to change sql code on every controller , but with models , changing just a method is enough .
Hope you understand my point of view . The example with that username, is of course a silly one , but will make things clear .