MySQL has a good reputation for its ease-of-use and the balance between high performance and scalability. In previous versions of MySQL5.5, MyISAM was the default storage engine for MySQL
According to our accumulated experience, most people will not change this default setting. In MySQL5.5 and later versions, the default storage engine for MySQL was modified to
The InnoDB. Similarly, we also hope that most users will not modify this default configuration. Benefit from this default InnoDB storage engine MySQL can give users to the RDBMS
Provides the properties of acid transactional, referential integrity, and failback. Below we will explore how to use the InnoDB table to improve your quality of life, whether you are a regular MySQL
User, or DBA, or developer.
Trends used by the storage engine
At the beginning of MySQL's development, the concurrency of early web-based applications was not very high and the requirements for high availability were not high. In recent years, hard drives and
Memory capacity and price/performance are very rapid increase. While focusing on MySQL, users are paying more attention to MySQL's reliability and failure recovery. MySQL database is strong
Large, robust, support for distributed
InnoDB can meet the needs of users. MySQL's storage engine has also switched to a more scalable innodb. So MySQL5.5 became the logical turn of the MySQL storage engine
Vertex: InnoDB becomes the default storage engine in MySQL5.5.
Only features that MyISAM can do in previous versions of MySQL can be innodb after MySQL5.6, including the following:
- InnoDB can build a full-text index (fulltext index)
- When using InnoDB to do read-only or read-mostly references, the performance is much better than before. Enable autocommit to refine the query, or through the start
The transaction read only statement starts a transaction, and it also optimizes reading-intensive applications.
- Applications that are stored on read-only devices can now also use the InnoDB engine.
InnoDB eventually became the default storage engine for MySQL
Starting with MySQL5.5.5, the default storage engine for creating tables becomes InnoDB. When creating a table, if you do not use the engine= syntax to develop the storage engine then the default
The InnoDB storage engine will be used.
The MySQL database and the INFORMATION_SCHEMA database are still used by the MyISAM storage engine and cannot be considered modified.
< to be continued ...>