mysql数据库中的外键约束详解（Detailed explanation of foreign key constraint in MySQL database）.docVIP

mysql数据库中的外键约束详解（Detailed explanation of foreign key constraint in MySQL database） People who have developed database driven small web applications using MySQL know that creating, retrieving, updating, and deleting tables of relational databases is a relatively simple process. In theory, as long as the master of the SQL statement is the most common usage, and familiar with your choice of server-side scripting language use, it is sufficient to meet the various need of the MySQL table operation, especially when you use the fast MyISAM database engine. But even in the simplest case, things are much more complicated than we think. Lets illustrate with a typical example. Suppose you are running a blog site, you update almost every day, and the site allows visitors to comment on your posts. In this case, our database schema should include at least two MyISAM tables, one for storing your blog posts, and the other for processing visitor comments. Obviously, there is a one to one relationship between the two tables, so we have to define a foreign key in the second table so that the database can be kept intact when updating or deleting data rows. Applications such as the above, not only maintaining the integrity of the two tables, are a severe challenge, but the biggest difficulty is that we must maintain their integrity at the application level. This is the method that most of the web projects that do not require transactions use during development because the MyISAM table can provide excellent performance. Of course, there is a cost, as I said before, the integrality and consistency of the application must maintain the database, which means to achieve more complex programming logic to handle the relationship between each table. Although database access can be simplified by using abstraction layers and ORM modules, the logic required to process them will undoubtedly become more complex as the number of data tables required by applications increases. So, for MySQL, there is n