Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 2
    because the pattern still works even if you regenerate the view every request. Commented Jun 24, 2021 at 8:35
  • But isn't the "model" in these frameworks strange? There aren't supposed to have methods on them, for example. It doesn't have to notify the UI of changes so that's fine in that regard. Commented Jun 24, 2021 at 8:53
  • 2
    I think you're looking too hard into this. In MVC, the general idea is that there is a controller that does something and in the end, produces a model that is given to a view (thus "MVC") that presents itself using the model data. The database entities are models, but not (or at least should not be) "MVC" models, they are models for ORM (obejct relational mapping) like entity frameworks. They are NOT MVC models. Commented Jun 24, 2021 at 9:02
  • 5
    The model in MVC can be anything, it does't have to be an ORM entity model as in the example. But for simple CRUD applications, the model is often ORM entities, so you will se that a lot in tutorials and examples. Commented Jun 24, 2021 at 9:24
  • Thank you JaquesB, that cleared it up for me. Seeing two types of model in apps with/ without an ORM was confusing me. Commented Jun 24, 2021 at 10:51