PHP interview question 8: The difference between innoDB and myisam

The content of this article is about the difference between innoDB and myisam in the eighth PHP interview question. It has a certain reference value. Now I share it with you. Friends in need can refer to it

InnoDB:
Support transaction processing, etc.
Read without locking
Support foreign keys
Support row locks
Do not support FULLTEXT type indexes
Do not save the specific number of rows in the table, scan the table to calculate the number of rows How many rows
When DELETE a table, it is deleted row by row
InnoDB stores data and indexes in the table space
Can be directly copied and used across platforms
InnoDB must contain an index of the AUTO_INCREMENT type field
The table is difficult to be compressed

MyISAM:
Transactions are not supported, rollback will cause incomplete rollback, and are not atomic
Does not support foreign keys
Does not support foreign keys
Support full-text search
Save the specific number of rows in the table. Without where, the number of saved rows will be returned directly
When DELETE the table, first drop the table and then rebuild the table
MyISAM table is stored in three files . The frm file stores table definitions. The data file is MYD (MYData). The index file is an extension of MYI (MYIndex)
It is difficult to copy directly across platforms
In MyISAM, the AUTO_INCREMENT type field can be used to create a joint index
The table can be compressed

Select:
Because MyISAM It is relatively simple, so it is better than InnoDB in terms of efficiency. If the system reads more and writes less. Low atomicity requirements. Then MyISAM is the best choice. And MyISAM recovery speed is fast. Can be directly overwritten and restored with backup.
If the system reads less and writes more, especially when concurrent writes are high. InnoDB is the first choice.
Both types have their own advantages and disadvantages. Which one you choose depends entirely on your actual type.

InnoDB:
Support transaction processing, etc.
Read without locking
Support foreign keys
Support row locks
Does not support FULLTEXT type indexes
Does not save the table The specific number of rows, scan the table to calculate how many rows there are
When DELETE the table, it is deleted row by row
InnoDB stores the data and indexes in the table space
Cross-platform can be directly copied and used
InnoDB The index of the AUTO_INCREMENT type field must be included
The table is difficult to be compressed

MyISAM:
Does not support transactions, rollback will cause incomplete rollback, and is not atomic
Does not support external Key
Does not support foreign keys
Supports full-text search
Save the specific number of rows in the table. Without where, the number of saved rows will be returned directly
When DELETE the table, first drop the table, and then rebuild the table
MyISAM tables are stored in three files. The frm file stores table definitions. The data file is MYD (MYData). The index file is an extension of MYI (MYIndex)
It is difficult to copy directly across platforms
In MyISAM, the AUTO_INCREMENT type field can be used to create a joint index
The table can be compressed

Select:
Because MyISAM It is relatively simple, so it is better than InnoDB in terms of efficiency. If the system reads more and writes less. Low atomicity requirements. Then MyISAM is the best choice. And MyISAM recovery speed is fast. Can be directly overwritten and restored with backup.
If the system reads less and writes more, especially when concurrent writes are high. InnoDB is the first choice.
Both types have their own advantages and disadvantages. Which one you choose depends entirely on your actual type.

Related recommendations:

php interview question 7: How to configure nginx load balancing

php interview question 6: memcache and redis Difference

php interview question 5: How nginx calls php and the role and working principle of php-fpm

The above is the detailed content of PHP interview question 8: The difference between innoDB and myisam. For more information, please follow other related articles on the PHP Chinese website!