Yesterday, someone in the group said that using MVC adds a lot of database operations to the program, which reduces performance. This really surprised me. MVC is just a framework and has nothing to do with database operations. MVC only provides a clear programming development model. As long as you handle it well, it is impossible to do a lot of unnecessary database operations. If an MVC allows a programmer to perform many more database operations without knowing it, it is definitely not a good MVC architecture. I think MVC only needs to provide a simple development framework. There is no need to integrate many library classes. It is best for programmers to choose to use library classes.
The purpose of my own MVC framework is just to implement a simple MVC process. Others can be added in detail according to your specific situation. Be truly compact, flexible and efficient!
I wrote two articles in the past few weeks, "The easiest way to implement MVC development in PHP - view and template technology", "The easiest way to implement MVC development in PHP - single point of entry". Today I will talk specifically about how to implement the MVC model.
I have not studied the theory of MVC in depth. For me personally, the model is a database encapsulation. By calling the model method, you can get the corresponding data, but the programmer does not need to care about the implementation details. In actual development, it is likely that a database table corresponds to a model. For example, a user information table userinfo corresponds to a model user. By calling the add() method of the model user, you can add a piece of data to the database, you can query it through select(), and you can update it through update. At the same time, the model should be independent of the specific database type, whether you use mysql, oracle or sql server. At the same time, I do not recommend using ROR in WEB development. It is so convenient and fast to use SQL language for complex multi-table queries, and the performance is better. If a programmer doesn't even have knowledge of SQL, I don't think he is a qualified programmer. Therefore, I provide a query method in my model to implement direct SQL query.
The following is an approximate result of the model. This is not the complete code. Please see the demo package for the complete code.
Copy the code The code is as follows:
class module{
var $mysql;//Database operation class, which can be mysql, oracle, sql, etc.
var $tbname;//Model correspondence Table name
var $debug=false;//Whether it is debug mode
function module($tbname,$db=''){}//Constructor
function _setDebug($debug=true){}//Turn on or Turn off debugging mode
function add($row,$tbname=''){}//Add a new record
function query($strsql){}//Query the sql statement directly
function count($where='',$ tbname=''){ }//Counting statistics
function select($where='',$tbname=''){}//Query
function delete($where='',$tbname=''){} //Delete a record that meets the conditions
function update($set,$where,$tbname=''){}//Update the specified record
function detail($where,$tbname=''){}//Detailed display A record
}
?>