Is it bad habit to work with multiple models in one controller action?
Should it always be like one controller-one model-one view?
Is it bad habit to work with multiple models in one controller action? Should
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is it bad habit to work with multiple models in one controller action?
Should it always be like one controller-one model-one view?
No, of course it is not a bad habit. Where you work with multiple tables, then various models will be needed.
The problem is not so much with this, but with the frameworks ability to handle advanced queries, joins and filtering based on these models. It’s one of those bugbears when you are “obliged” to follow a framework’s particular aesthetic about database interaction, but this depends on, of course, which framework and how far you are relying on magic behaviours.
Not every project is a simple blog! 🙂
edit: I should say also, that this kind of thing is one of my main gripes with MVC frameworks in general. The compromise between what your project is attempting to achieve, and what the framework allows is always going to be where the hair is lost and the late nights invested..