- Documentation Library
- Table of Contents
- MySQL 5.5 Manual
- MySQL 5.4 Manual
- MySQL 5.1 Manual
- MySQL 5.0 Manual
- MySQL 3.23/4.0/4.1 Manual
- Table of Contents
MySQL 3.23, 4.0, 4.1 Reference Manual :: 13 Storage Engines :: 13.2 The InnoDB Storage Engine :: 13.2.11 InnoDB Table and Index Structures
Section Navigation [Toggle]
- 13.2 The InnoDB Storage Engine
- 13.2.1 InnoDB Contact Information
- 13.2.2 InnoDB in MySQL 3.23
- 13.2.3 InnoDB Configuration
- 13.2.4 InnoDB Startup Options and System Variables
- 13.2.5 Creating and Using InnoDB Tables
- 13.2.6 Adding, Removing, or Resizing InnoDB Data and Log Files
- 13.2.7 Backing Up and Recovering an InnoDB Database
- 13.2.8 Moving an InnoDB Database to Another Machine
- 13.2.9 The InnoDB Transaction Model and Locking
- 13.2.10 InnoDB Multi-Versioning
- 13.2.11 InnoDB Table and Index Structures
- 13.2.12 InnoDB Disk I/O and File Space Management
- 13.2.13 InnoDB Error Handling
- 13.2.14 InnoDB Performance Tuning and Troubleshooting
- 13.2.15 Restrictions on InnoDB Tables
[+/-]
MySQL stores its data dictionary information for tables in
.frm files in database directories. This is
true for all MySQL storage engines, but every
InnoDB table also has its own entry in the
InnoDB internal data dictionary inside the
tablespace. When MySQL drops a table or a database, it has to
delete one or more .frm files as well as the
corresponding entries inside the InnoDB data
dictionary. Consequently, you cannot move
InnoDB tables between databases simply by
moving the .frm files. It is also the reason
why DROP DATABASE did not work for
InnoDB type tables before MySQL 3.23.44.
User Comments
Add your own comment.