Mysql series (4) storage engine

MyISAMMySQL The default database engine before 5.0 is the most commonly used. Has high insertion and query speed, but does not support transactions

InnoDB is the preferred engine for transactional databases, supports ACID transactions, supports row-level locking, and has become the default database engine since MySQL 5.5

BDB is derived from Berkeley DB, a transactional database Another option that supports other transaction features such as Commit and Rollback

Memory is a storage engine that places all data in memory and has extremely high insertion, update and query efficiency. But it will occupy memory space proportional to the amount of data. And its content will be lost when MySQL is restarted

Merge combines a certain number of MyISAM tables into a whole, which is very useful for very large-scale data storage

Archive is very suitable for storing a large amount of independent data as a historical record. Because they are not read often. Archive has efficient insertion speed, but its support for queries is relatively poor

Federated combines different MySQL servers to logically form a complete database. Very suitable for distributed applications

Cluster/NDB highly redundant storage engine, using multiple data machines to jointly provide services to improve overall performance and security. Suitable for applications with large amounts of data and high security and performance requirements

CSV: A storage engine that logically separates data by commas. It creates a .csv file for each data table in the database subdirectory. This is a normal text file, with each line of data occupying one text line. The CSV storage engine does not support indexing.

BlackHole: Black hole engine, any data written will disappear, generally used to record binlog as a relay for replication

EXAMPLE storage engine is a stub engine that does not do anything. It is intended as an example in the MySQL source code to demonstrate how to start writing a new storage engine. Again, its main interest is to developers. EXAMPLE The storage engine does not support indexing.

In addition, MySQL’s storage engine interface is well defined. Interested developers can write their own storage engines by reading the documentation.

The above is the content of the Mysql series (4) storage engine. For more related content, please pay attention to the PHP Chinese website (www.php.cn)!