Questions about the role of model in mvc pattern

The m (model) in mvc represents the model, which is mainly used to manipulate data. So whether simple processing of data should be done in the C layer or the M layer.

<code>$sql = "SELECT id, name FROM test_table"
$result = $conn->query($sql);
$data = $result->getAll();</code>

In the above code, if I need to change data into an array with id as the key, should this operation be performed on layer m or layer c?

Reply content:

The m (model) in mvc represents the model, which is mainly used to manipulate data. So whether simple processing of data should be done in the C layer or the M layer.

<code>$sql = "SELECT id, name FROM test_table"
$result = $conn->query($sql);
$data = $result->getAll();</code>

In the above code, if I need to change data into an array with id as the key, should this operation be performed on layer m or layer c?

Personal opinion: M layer is better
Since you use MVC, it is to reduce the degree of coupling and improve scalability.
Writing mixed words is not conducive to the above two purposes.
Of course, if the project itself is not large, there is actually no need to use the mvc structure.

According to the problem in your example, I think you can use the closure function method. For example, define a dataFormat method in the model class, and then call it when returning the data. This dataFormat then uses the closure you passed in the class. function to process your return data, which is more flexible

In fact, it all works. It depends on your interface requirements. Don’t worry too much! Because of this question, I also asked my teacher. I said that the C layer is responsible for controlling page jumps and encapsulating the request data retrieval interface, while the M layer is responsible for verifying the parameters of the C layer call interface and data processing return. What is the specific business? Where to put the logic? In fact, this is all done according to the needs of our own program design

So don’t worry too much

The emergence of model is to control all the data layer in the model. Why do you do this?

<code>耦合性降低了、可读性、维护、扩展性都得到了提高。
</code>

c in mvc is used to connect model and view

The core idea of ​​MVC is to separate the interface (View), logic (Controller), and data (Model).
For web applications, the process is C calling M and outputting V.

Page Controller:

<code>/post.php?a=create
/post.php?a=read&id=1024
/post.php?a=update&id=1024
/post.php?a=delete&id=1024</code>

Model (CRUD):

<code>function post_create() {}
function post_read() {}
function post_update() {}
function post_delete() {}</code>

View:
/view/post.php

It can be seen that the CRUD operation functions for the data model post are of course summarized in /include/funclass.php so that they can be called in other controllers. In short, if you think you need to use this operation in other controllers, Then you can consider encapsulating it into a function or class and putting it in funclass.php for "sharing".

It must be operated in the controller

Bold textPlease enter the code

---

---