14.1 Introduction to InnoDB

14.1.1 Benefits of Using InnoDB Tables
14.1.2 Best Practices for InnoDB Tables
14.1.3 Checking InnoDB Availability
14.1.4 Testing and Benchmarking with InnoDB
14.1.5 Turning Off InnoDB
InnoDB is a general-purpose storage engine that balances high reliability and high performance. In MySQL 5.7, InnoDB is the default MySQL storage engine. Unless you have configured a different default storage engine, issuing a CREATE TABLE statement without an ENGINE= clause creates an InnoDB table.
InnoDB是一個平衡了高可靠性和高性能的通用存儲引擎,在mysql5.7中，innodb是mysql的默認存儲引擎，除非配置了不同的默認存儲引擎，執行create_table語句沒有ENGINE=子句的情況下默認創建innodb表
Key Advantages of InnoDB

innodb包含以下優勢

• Its DML operations follow the ACID model, with transactions featuring commit, rollback, and crash-recovery capabilities to protect user data. See Section 14.2, “InnoDB and the ACID Model” for more information.
• DML操作遵循ACID模式，擁有commit,rollaback,crash_recovery等事務功能來保護用戶的數據,更多信息請查看 Section 14.2, “InnoDB and the ACID Model”
• Row-level locking and Oracle-style consistent reads increase multi-user concurrency and performance. See Section 14.5, “InnoDB Locking and Transaction Model” for more information.
• 行級鎖和oracle風格的一致讀提高了多用戶併發性和性能，更多信息請看 Section 14.5, “InnoDB Locking and Transaction Model”
• InnoDB tables arrange your data on disk to optimize queries based on primary keys. Each InnoDB table has a primary key index called the clustered index that organizes the data to minimize I/O for primary key lookups. See Section 14.8.2.1, “Clustered and Secondary Indexes” for more information.
• InnoDB表將您的數據放在磁盤上，以優化基於主鍵的查詢。每個InnoDB表都有一個主鍵索引，稱爲聚集索引，它組織數據以最小化主鍵查找的I/O。更多信息請看Section 14.8.2.1, “Clustered and Secondary Indexes”
• To maintain data integrity, InnoDB supports FOREIGN KEY constraints. With foreign keys, inserts, updates, and deletes are checked to ensure they do not result in inconsistencies across different tables. See Section 14.8.1.6, “InnoDB and FOREIGN KEY Constraints” for more information.
• 爲了維護數據的完整性，innodb支持外鍵約束,數據的inserts,updtes,deletes操作都會被檢查，確保它們不會導致不同表之間的不一致。
  
  [a] InnoDB support for geospatial indexing is available in MySQL 5.7.5 and later.
  在mysql5.7.5以及之後的版本，innodb支持空間索引
  [b] InnoDB utilizes hash indexes internally for its Adaptive Hash Index feature
  innodb內部也有哈希索引，叫做自適應哈希索引
  [c] InnoDB support for FULLTEXT indexes is available in MySQL 5.6.4 and later.
  在mysql5.6.4以及之後的版本 innodb支持全文索引
  [d] Compressed InnoDB tables require the InnoDB Barracuda file format.
  壓縮Innodb表需要InnoDB Barracuda文件格式。
  [e] Implemented in the server (via encryption functions). Data-at-rest tablespace encryption is available in MySQL 5.7 and later.
  在服務層中實現（通過加密函數）。MySQL 5.7和以後可用的表空間加密數據。
  [f] Implemented in the server, rather than in the storage engine.
  在服務層實現，而不是在存儲引擎中實現
  [g] Implemented in the server, rather than in the storage engine.
  To compare the features of InnoDB with other storage engines provided with MySQL, see the Storage Engine Features table inChapter 15, Alternative Storage Engines.
  將InnoDB的特性與MySQL提供的其他存儲引擎進行比較。關於存儲引擎特性表，請查看Chapter 15, Alternative Storage Engines.
  InnoDB Enhancements and New Features

For information about InnoDB enhancements and new features in MySQL 5.7, refer to:
查看mysql的增強功能和新功能

• The InnoDB enhancements list in Section 1.4, “What Is New in MySQL 5.7”.
• InnoDB增強列表，請看Section 1.4, “What Is New in MySQL 5.7”.
• The Release Notes.
  Additional InnoDB Information and Resources

innodb的額外信息和資源

• For InnoDB-related terms and definitions, see MySQL Glossary.
• innodb的相關術語和定義
• For a forum dedicated to the InnoDB storage engine, see MySQL Forums::InnoDB.
• 一個討論innodb引擎的論壇
• InnoDB is published under the same GNU GPL License Version 2 (of June 1991) as MySQL. For more information on MySQL licensing, see http://www.mysql.com/company/legal/licensing/.