
AVG_ROW_LENGTH is the average rows size. It only applies to tables using
MyISAM and Aria storage engines that have the ROW_FORMAT table option set to
FIXED format.

MyISAM uses MAX_ROWS and AVG_ROW_LENGTH to decide the maximum size of a table
(default: 256TB, or the maximum file size allowed by the system).

[DEFAULT] CHARACTER SET/CHARSET
-------------------------------

[DEFAULT] CHARACTER SET (or [DEFAULT] CHARSET) is used to set a default
character set for the table. This is the character set used for all columns
where an explicit character set is not specified. If this option is omitted or
DEFAULT is specified, database's default character set will be used. See
Setting Character Sets and Collations for details on setting the character
sets.

CHECKSUM/TABLE_CHECKSUM
-----------------------

CHECKSUM (or TABLE_CHECKSUM) can be set to 1 to maintain a live checksum for
all table's rows. This makes write operations slower, but CHECKSUM TABLE will
be very fast. This option is only supported for MyISAM and Aria tables.

[DEFAULT] COLLATE
-----------------

[DEFAULT] COLLATE is used to set a default collation for the table. This is
the collation used for all columns where an explicit character set is not
specified. If this option is omitted or DEFAULT is specified, database's
default option will be used. See Setting Character Sets and Collations for
details on setting the collations

COMMENT
-------

COMMENT is a comment for the table. The maximum length is 2048 characters.
Also used to define table parameters when creating a Spider table.

CONNECTION
----------

CONNECTION is used to specify a server name or a connection string for a
Spider, CONNECT, Federated or FederatedX table.

DATA DIRECTORY/INDEX DIRECTORY
------------------------------

DATA DIRECTORY and INDEX DIRECTORY are supported for MyISAM and Aria, and DATA
DIRECTORY is also supported by InnoDB if the innodb_file_per_table server
system variable is enabled, but only in CREATE TABLE, not in ALTER TABLE. So,
carefully choose a path for InnoDB tables at creation time, because it cannot
be changed without dropping and re-creating the table. These options specify
the paths for data files and index files, respectively. If these options are
omitted, the database's directory will be used to store data files and index
files. Note that these table options do not work for partitioned tables (use
the partition options instead), or if the server has been invoked with the
--skip-symbolic-links startup option. To avoid the overwriting of old files
with the same name that could be present in the directories, you can use the
--keep_files_on_create option (an error will be issued if files already
exist). These options are ignored if the NO_DIR_IN_CREATE SQL_MODE is enabled
(useful for replication slaves). Also note that symbolic links cannot be used
for InnoDB tables.

DATA DIRECTORY works by creating symlinks from where the table would normally
have been (inside the datadir) to where the option specifies. For security
reasons, to avoid bypassing the privilege system, the server does not permit
symlinks inside the datadir. Therefore, DATA DIRECTORY cannot be used to
specify a location inside the datadir. An attempt to do so will result in an
error 1210 (HY000) Incorrect arguments to DATA DIRECTORY.

DELAY_KEY_WRITE
---------------

DELAY_KEY_WRITE is supported by MyISAM and Aria, and can be set to 1 to speed
up write operations. In that case, when data are modified, the indexes are not
updated until the table is closed. Writing the changes to the index file
altogether can be much faster. However, note that this option is applied only
if the delay_key_write server variable is set to 'ON'. If it is 'OFF' the
delayed index writes are always disabled, and if it is 'ALL' the delayed index
writes are always used, disregarding the value of DELAY_KEY_WRITE.

ENCRYPTED
---------

The ENCRYPTED table option can be used to manually set the encryption status
of an InnoDB table. See InnoDB Encryption for more information.

Aria does not support the ENCRYPTED table option. See MDEV-18049.

See Data-at-Rest Encryption for more information.

ENCRYPTION_KEY_ID
-----------------

The ENCRYPTION_KEY_ID table option can be used to manually set the encryption
key of an InnoDB table. See InnoDB Encryption for more information.

Aria does not support the ENCRYPTION_KEY_ID table option. See MDEV-18049.

See Data-at-Rest Encryption for more information.

IETF_QUOTES
-----------

For the CSV storage engine, the IETF_QUOTES option, when set to YES, enables
IETF-compatible parsing of embedded quote and comma characters. Enabling this
option for a table improves compatibility with other tools that use CSV, but
is not compatible with MySQL CSV tables, or MariaDB CSV tables created without
this option. Disabled by default.

INSERT_METHOD
-------------

INSERT_METHOD is only used with MERGE tables. This option determines in which
underlying table the new rows should be inserted. If you set it to 'NO' (which
is the default) no new rows can be added to the table (but you will still be
able to perform INSERTs directly against the underlying tables). FIRST means
that the rows are inserted into the first table, and LAST means that thet are
inserted into the last table.

KEY_BLOCK_SIZE
--------------

KEY_BLOCK_SIZE is used to determine the size of key blocks, in bytes or
kilobytes. However, this value is just a hint, and the storage engine could