Form validation not in controller but rather in Model

[eluser]mi6crazyheart[/eluser]

Code:

moreover dealing with data checking in a controller is not perhaps the good manner to do.

May it's u'r personal style of working or it's logic that need such kind of data flow... but, as far as MVC approach concern, CONTROLLER is made for controlling any kind of checking & validation in the 1st entry stage of the application. Then, after checking it's CONTROLLER should be decide what kind of action taken over the request it has received. In this way it's act like a protective shield to any application.

About MODEL, it's a section which directly work with DB. So, may be there are chances if any thing will go wrong then it's effect directly on u'r DB data.

So in my suggestion , if u'r application has no specific necessary which need form validation at MODEL side then complete all those jobs in controller side.