Skip navigation links
Falcon Storage Engine Guide :: 3 Creating the Falcon Tablespace
4 Creating Tables and Indexes within Falcon »
Section Navigation      [Toggle]

Chapter 3. Creating the Falcon Tablespace

Within Falcon, all data within one database is stored within a tablespace file within the MySQL directory structure. By default, the falcon_user tablespace file will be used for table storage, irrespective of the table's MySQL database schema.

Falcon also supports named tablespaces which allow you to store tables within specific files that may be different to the default Falcon storage file for that database. Three Falcon tablespaces are created automatically when the Falcon storage engine is enabled within the server. These tables are:

  • An unnamed internal tablespace used to hold system tables.

  • falcon_user, used as the default location for user defined tables.

  • falcon_temporary, used to hold temporary tables.

All tablespaces share the same log files, memory and threads. Transactions run transparently across all tablespaces. There is no inherent relationship between a tablespace and the database/schema to which it relates.

To create a new tablespace, use the CREATE TABLESPACE statement: 

CREATE TABLESPACE tablespace_name
    ADD DATAFILE 'file_name'
    ENGINE [=] Falcon

Note

From MySQL 6.0.10, all Falcon tablespaces are created with a .fts extension. If you do not specify the extension explicitly, the extension will be added before the tablespace file is created.

Two further files are created by Falcon, and these contain the on-disk copy of the Falcon serial log. The log files are named falcon_master.fl1 and falcon_master.fl2.

Table definitions are, as with the other MySQL engines, stored within a .frm file within a database specific directory. For example, the table falcontest within the test database will create the table definition file falcontest.frm within the directory test.