MySQL's enterprise-grade solution with high availability and robust data integrity
MySQL transactions, row-level locking, hot backup, and foreign key support - without sacrificing MySQL's high-speed performance
1 InnoDB tables overview
1.1 Differences between MySQL/InnoDB releases
2 InnoDB startup options
3 Create an InnoDB database
3.1 Several errors that may occur when establishing a database
3.2 Shut down the MySQL server
4 Create InnoDB table
4.1 How to use transactions in InnoDB
4.2 Convert MyISAM table to InnoDB type
4.3 Foreign key constraints
4.4 How auto-increment works in InnoDB
4.5 InnoDB and MySQL replication
5 Add and remove InnoDB data and log files
6 Backing up and restoring an InnoDB database
6.1 Forcing recovery
6.2 Checkpoints
7 Move the InnoDB database to another machine
8 InnoDB transaction mode and locking
8.1 Consistent read
8.2 Locking reads
8.3 Next-key locking: avoiding the phantom problem
8.4 Lock settings for each SQL statement in InnoDB
8.5 When does MySQL implicitly commit or rollback a transaction?
8.6 Deadlock detection and rollback
8.7 Example of consistent read operation in InnoDB
8.8 How to deal with deadlocks
9 Performance Tuning Tips
9.1InnoDB Monitors (Monitors)
10 implementation of multiversioning
11 Table and index structure
11.1 Physical structure of the index
11.2 Insert buffer
11.3 Adaptive hash indexes
11.4 Physical structure of the record
12 File space management and disk I/O
12.1 Disk I/O and raw devices
12.2 File space management
12.3 Defragmenting a table
13 Error handling
13.1 Some error codes returned by MySQL
13.2 Error coding in some operating systems
14 Limitations of InnoDB tables
15 Fault detection and repair
15.1 Operations to find and fix data dictionary errors
16 InnoDB version history
17 Contact information
18 The GNU GPL License Version 2
19 Known bugs and their fixes in old versions of InnoDB
20 The TODO list of new features to InnoDB
21 Some books and articles on MySQL/InnoDB
