What is the difference between the role of M and C in the MVC pattern?

What is the difference between the role of M and C in the MVC pattern? For example, the establishment of a student information management system, M can change the student information and search, Operation database. What do you need to do with layer C? Of course, the C-tier can also use SQL to manipulate the database

Reply to discussion (solution)

The division of MVC is artificially divided, and there is no definite boundary
Generally speaking, M is the business logic. That is, everything that is relevant to the business (except the user interface) should be placed here
Because the database is related to the specific business, it should not be placed in C (not to say that C cannot manipulate the database, but you force yourself not to access the database in C)

M is the data layer for data acquisition
C is the control layer for logic control

You can understand that.

M is data, C is how to control how the data is used, V is how to display the data.

The division of MVC is artificially divided, and there is no definite boundary
Generally speaking, M is the business logic. That is, everything that is relevant to the business (except the user interface) should be placed here
Because the database is related to the specific business, it should not be placed in C (not to say that C cannot manipulate the database, but you force yourself not to access the database in C)

+1 See some open source code feel m and C difference does not capitalize in M method can also be written in C, written in C can also put in M, so have been very confused what is the difference

