- 13 Storage Engines
- 13.1 Comparing Transaction and Nontransaction Engines
- 13.2 Other Storage Engines
- 13.3 Setting the Storage Engine
- 13.4 Overview of MySQL Storage Engine Architecture
- 13.5 The MyISAM Storage Engine
- 13.6 The InnoDB Storage Engine
- 13.7 The IBMDB2I Storage Engine
- 13.8 The MERGE Storage Engine
- 13.9 The MEMORY (HEAP) Storage Engine
- 13.10 The EXAMPLE Storage Engine
- 13.11 The FEDERATED Storage Engine
- 13.12 The ARCHIVE Storage Engine
- 13.13 The CSV Storage Engine
- 13.14 The BLACKHOLE Storage Engine
[+/-]
- 13.7.1. Installation
- 13.7.2. Configuration Options
- 13.7.3. Creating schemas and tables
- 13.7.4. Database/metadata management
- 13.7.5. Transaction behavior
- 13.7.6. Principles and Terminology
- 13.7.7. Notes and Limitations
- 13.7.8. Character sets and collations
- 13.7.9. Error codes and trouble-shooting information
The IBMDB2I storage engine is designed as a fully
featured transaction-capable storage engine that enables MySQL to
store its data in DB2 tables running on IBM i. With the
IBMDB2I storage engine, data can be shared
between MySQL applications and applications coded for native DB2 for
i interfaces.
IBMDB2I provides ACID-compliant transactions,
support for foreign key constraints, full crash recovery,
radix-tree-based indexes, and the unique ability to allow DB2 for i
applications to see and update table data in real time.
More information about the storage engine and its interaction with DB2 for i can be found in IBM's Using DB2 for i as a Storage Engine for MySQL Redbook publication, at IBM DB2 for i a Storage Engine for MySQL Redbook.
The IBMDB2I storage engine was introduced in
MySQL 5.1.33 and considered GA in MySQL 5.1.35.
User Comments
Add your own comment.