InnoDB Chinese Reference Manual---InnoDB Tables overview

Reference Manual | Chinese InnoDB chinese reference Manual---Dog dog (heart sail) 1 InnoDB Tables Overview
InnoDB provides MySQL with transaction security (commit), rollback (rollback), and crash repair (crash recovery capabilities) (Transaction-safe (ACID compliant ) Type table. InnoDB provides a row lock (locking on row level) that provides an unlocked read (non-locking read in selects) consistent with the Oracle type. These features improve the performance of multi-user concurrency operations. You do not need to extend the lock (lock escalation) in the InnoDB table because InnoDB column locks (row level locks) are suitable for very small spaces. InnoDB is the first table engine on MySQL that provides a foreign key constraint (FOREIGN key constraints).

InnoDB's design goal is to handle a large-capacity database system, which is not comparable to other disk-based relational database engines.

Technically, InnoDB is a complete database system in the MySQL background, InnoDB to build its dedicated buffer pool in main memory for caching data and indexing. InnoDB the data and index in a tablespace, possibly containing multiple files, unlike other, for example, in MyISAM, tables are stored in separate files. The size of the InnoDB table is limited to the file size of the operating system, typically 2 GB.

The latest information on InnoDB can be found on the http://www.innodb.com/. The latest version of the InnoDB manual is always placed there, where it can get InnoDB's business license (order commercial licenses) and support.

InnoDB is now (October 2001) used in a number of large database sites that require high performance. The famous Internet news site slashdot.org is the use of InnoDB. Mytrix, Inc. stores more than 1 TB of data on the InnoDB table, and another site handles an average of 800 insert/update loads per second on the InnoDB table.

In the MySQL source code, the InnoDB table engine is included from 3.23.34a and activated in the binary version of Mysql-max.

In order to use the InnoDB table engine, the InnoDB boot configuration must be specified in the ' my.cnf ' or ' my.ini ' file in detail. The least modified method is to add the following line to the [mysqld] area:

innodb_data_file_path=ibdata:30m

But to get the best performance Recommendation specify configuration options in detail, view 2 InnoDB Startup options.

InnoDB is licensed under the GNU GPL version 2 (June 1991).
The difference between 1.1 Mysql/innodb release versions
Mysql-max-3.23: This is a stable version and is recommended for use by the product. MySQL-4.0: This is a development version that contains some new features, such as multiple table deletions (multi-table delete), query result buffering (cached query results), and SSL communications, compared to MySQL 3.23. The InnoDB table engine in version 4.0 and version 3.23 is the same. The stability of the 4.0.1 can be categorized as beta. MySQL-4.0 Embedded server library:you can link this into your application. The benefits are easier deployment for your application, better performance, and easier use. The stability of the embedded library is classified as alpha, but it should to be gamma within a few months.