Table Name表名称

Temporary Tables临时表

Table Cloning and Copying表克隆和表复制

Column Data Types and Attributes列数据类型和属性

Indexes, Foreign Keys, and CHECK Constraints索引约束、外键约束和检查约束

Table Options表格选项

Table Partitioning表分区

tbl_name

The table name can be specified as db_name.tbl_name to create the table in a specific database. 可以将表名指定为db_name.tbl_name，以便在特定数据库中创建表。This works regardless of whether there is a default database, assuming that the database exists. 无论是否存在默认数据库（假设该数据库存在），此操作都有效。If you use quoted identifiers, quote the database and table names separately. 如果使用带引号的标识符，请分别引用数据库和表名。For example, write `mydb`.`mytbl`, not `mydb.mytbl`.例如，写`mydb`.`mytbl`，而不是`mydb.mytbl`。

Rules for permissible table names are given in Section 9.2, “Schema Object Names”.第9.2节，“模式对象名称”中给出了允许表名称的规则。

IF NOT EXISTS

Prevents an error from occurring if the table exists. 防止表存在时发生错误。However, there is no verification that the existing table has a structure identical to that indicated by the CREATE TABLE statement.但是，无法验证现有表是否具有与CREATE TABLE语句所指示的结构相同的结构。

LIKE

Use CREATE TABLE ... LIKE to create an empty table based on the definition of another table, including any column attributes and indexes defined in the original table:使用CREATE TABLE ... LIKE以基于另一个表的定义创建空表，包括原始表中定义的任何列属性和索引：

CREATE TABLE new_tbl LIKE orig_tbl;

For more information, see Section 13.1.20.3, “CREATE TABLE ... LIKE Statement”.有关更多信息，请参阅第13.1.20.3节，“CREATE TABLE ... LIKE语句”。

[AS] query_expression

To create one table from another, add a SELECT statement at the end of the CREATE TABLE statement:要从一个表创建另一个表，请在create table语句末尾添加SELECT语句：

CREATE TABLE new_tbl AS SELECT * FROM orig_tbl;

For more information, see Section 13.1.20.4, “CREATE TABLE ... SELECT Statement”.有关更多信息，请参阅第13.1.20.4节，“CREATE TABLE ... SELECT语句”。

The IGNORE and REPLACE options indicate how to handle rows that duplicate unique key values when copying a table using a SELECT statement.IGNORE和REPLACE选项指示在使用SELECT语句复制表时如何处理重复唯一键值的行。

For more information, see Section 13.1.20.4, “CREATE TABLE ... SELECT Statement”.有关更多信息，请参阅第13.1.20.4节，“CREATE TABLE ... SELECT语句”。

data_type

data_type represents the data type in a column definition. data_type表示列定义中的数据类型。For a full description of the syntax available for specifying column data types, as well as information about the properties of each type, see Chapter 11, Data Types.有关可用于指定列数据类型的语法的完整描述，以及有关每种类型的属性的信息，请参阅第11章，“数据类型”。

NOT NULL | NULL

If neither NULL nor NOT NULL is specified, the column is treated as though NULL had been specified.如果既不指定NULL也不指定NOT NULL，则该列将被视为已指定NULL。

In MySQL 8.0, only the InnoDB, MyISAM, and MEMORY storage engines support indexes on columns that can have NULL values. 在MySQL 8.0中，只有InnoDB、MyISAM和MEMORY存储引擎支持可以有NULL值的列上的索引。In other cases, you must declare indexed columns as NOT NULL or an error results.在其他情况下，必须将索引列声明为NOT NULL否则会产生错误。

DEFAULT

Specifies a default value for a column. 指定列的默认值。For more information about default value handling, including the case that a column definition includes no explicit DEFAULT value, see Section 11.6, “Data Type Default Values”.有关默认值处理的更多信息，包括列定义不包含显式DEFAULT的情况，请参阅第11.6节，“数据类型默认值”。

If the NO_ZERO_DATE or NO_ZERO_IN_DATE SQL mode is enabled and a date-valued default is not correct according to that mode, CREATE TABLE produces a warning if strict SQL mode is not enabled and an error if strict mode is enabled. 如果启用了NO_ZERO_DATE或NO_ZERO_IN_DATESQL模式，并且根据该模式，日期值默认值不正确，则如果未启用严格SQL模式，CREATE TABLE将生成警告；如果启用严格模式，CREATE TABLE将生成错误。For example, with NO_ZERO_IN_DATE enabled, c1 DATE DEFAULT '2010-00-00' produces a warning.例如，如果启用了NO_ZERO_IN_DATE，c1 DATE DEFAULT '2010-00-00'将生成警告。

VISIBLE, INVISIBLE

Specify column visibility. 指定列可见性。The default is VISIBLE if neither keyword is present. 如果两个关键字都不存在，则默认值是VISIBLE。A table must have at least one visible column. 表必须至少有一个可见列。Attempting to make all columns invisible produces an error. 试图使所有列不可见会产生错误。For more information, see Section 13.1.20.10, “Invisible Columns”.有关更多信息，请参阅第13.1.20.10节，“不可见列”。

The VISIBLE and INVISIBLE keywords are available as of MySQL 8.0.23. VISIBLE关键字和INVISIBLE关键字从MySQL 8.0.23开始提供。Prior to MySQL 8.0.23, all columns are visible.在MySQL 8.0.23之前，所有列都是可见的。

AUTO_INCREMENT

An integer or floating-point column can have the additional attribute AUTO_INCREMENT. 整数或浮点列可以具有附加属性AUTO_INCREMENT。When you insert a value of NULL (recommended) or 0 into an indexed AUTO_INCREMENT column, the column is set to the next sequence value. 在索引自动增量列中插入NULL（建议）或0值时，该列将设置为下一个序列值。Typically this is value+1, where value is the largest value for the column currently in the table. 通常这是value+1，其中值是表中当前列的最大值。AUTO_INCREMENT sequences begin with 1.AUTO_INCREMENT序列从1开始。

To retrieve an AUTO_INCREMENT value after inserting a row, use the LAST_INSERT_ID() SQL function or the mysql_insert_id() C API function. 要在插入行后检索AUTO_INCREMENT值，请使用SQL函数LAST_INSERT_ID()或C API函数mysql_insert_id()。See Section 12.16, “Information Functions”, and mysql_insert_id().请参阅第12.16节，“信息函数”和mysql_insert_id()。

If the NO_AUTO_VALUE_ON_ZERO SQL mode is enabled, you can store 0 in AUTO_INCREMENT columns as 0 without generating a new sequence value. 如果启用了NO_AUTO_VALUE_ON_ZEROSQL 模式，则可以在AUTO_INCREMENT列中将0存储为0，而无需生成新的序列值。See Section 5.1.11, “Server SQL Modes”.请参阅第5.1.11节，“服务器SQL模式”。

There can be only one AUTO_INCREMENT column per table, it must be indexed, and it cannot have a DEFAULT value. 每个表只能有一个AUTO_INCREMENT列，它必须被索引，并且不能有DEFAULT值。An AUTO_INCREMENT column works properly only if it contains only positive values. 仅当AUTO_INCREMENT列仅包含正值时，该列才能正常工作。Inserting a negative number is regarded as inserting a very large positive number. 插入负数被视为插入非常大的正数。This is done to avoid precision problems when numbers “wrap” over from positive to negative and also to ensure that you do not accidentally get an AUTO_INCREMENT column that contains 0.这样做是为了避免数字从正数“换行”到负数时出现精度问题，也为了确保不会意外地得到包含0的AUTO_INCREMENT列。

For MyISAM tables, you can specify an AUTO_INCREMENT secondary column in a multiple-column key. 对于MyISAM表，您可以在多列键中指定AUTO_INCREMENT辅助列。See Section 3.6.9, “Using AUTO_INCREMENT”.请参阅第3.6.9节，“使用自动增量”。

To make MySQL compatible with some ODBC applications, you can find the AUTO_INCREMENT value for the last inserted row with the following query:要使MySQL与某些ODBC应用程序兼容，可以通过以下查询找到最后插入行的AUTO_INCREMENT值：

SELECT * FROM tbl_name WHERE auto_col IS NULL

This method requires that sql_auto_is_null variable is not set to 0. 此方法要求sql_auto_is_null变量未设置为0。See Section 5.1.8, “Server System Variables”.请参阅第5.1.8节，“服务器系统变量”。

For information about InnoDB and AUTO_INCREMENT, see Section 15.6.1.6, “AUTO_INCREMENT Handling in InnoDB”. 有关InnoDB和自动增量的信息，请参阅第15.6.1.6节，“InnoDB中的自动增量处理”。For information about AUTO_INCREMENT and MySQL Replication, see Section 17.5.1.1, “Replication and AUTO_INCREMENT”.有关AUTO_INCREMENT和MySQL复制的信息，请参阅第17.5.1.1节，“复制和自动增量”。

COMMENT

A comment for a column can be specified with the COMMENT option, up to 1024 characters long. 可以使用COMMENT选项指定列的注释，最长可达1024个字符。The comment is displayed by the SHOW CREATE TABLE and SHOW FULL COLUMNS statements.注释由SHOW CREATE TABLE和SHOW FULL COLUMNS语句显示。

COLUMN_FORMAT

In NDB Cluster, it is also possible to specify a data storage format for individual columns of NDB tables using COLUMN_FORMAT. 在NDB集群中，还可以使用COLUMN_FORMAT为NDB表的各个列指定数据存储格式。Permissible column formats are FIXED, DYNAMIC, and DEFAULT. 允许的列格式为FIXED、DYNAMIC和DEFAULT。FIXED is used to specify fixed-width storage, DYNAMIC permits the column to be variable-width, and DEFAULT causes the column to use fixed-width or variable-width storage as determined by the column's data type (possibly overridden by a ROW_FORMAT specifier).FIXED用于指定固定宽度存储，DYNAMIC允许列为可变宽度，而DEFAULT会导致列使用由列的数据类型确定的固定宽度或可变宽度存储（可能由ROW_FORMAT说明符覆盖）。

For NDB tables, the default value for COLUMN_FORMAT is FIXED.对于NDB表格，COLUMN_FORMAT的默认值是固定的。

In NDB Cluster, the maximum possible offset for a column defined with COLUMN_FORMAT=FIXED is 8188 bytes. 在NDB集群中，使用COLUMN_FORMAT=FIXED定义的列的最大可能偏移量为8188字节。For more information and possible workarounds, see Section 23.1.7.5, “Limits Associated with Database Objects in NDB Cluster”.有关更多信息和可能的解决方法，请参阅第23.1.7.5节，“NDB集群中与数据库对象相关的限制”。

COLUMN_FORMAT currently has no effect on columns of tables using storage engines other than NDB. COLUMN_FORMAT目前对使用NDB以外的存储引擎的表的列没有影响。MySQL 8.0 silently ignores COLUMN_FORMAT.MySQL 8.0默认忽略COLUMN_FORMAT。

ENGINE_ATTRIBUTE and SECONDARY_ENGINE_ATTRIBUTE options (available as of MySQL 8.0.21) are used to specify column attributes for primary and secondary storage engines. ENGINE_ATTRIBUTE和SECONDARY_ENGINE_ATTRIBUTE选项（从MySQL 8.0.21开始提供）用于指定主存储引擎和辅助存储引擎的列属性。The options are reserved for future use.这些选项保留供将来使用。

Permitted values are a string literal containing a valid JSON document or an empty string (''). 允许的值是包含有效JSON文档的字符串文字或空字符串（''）。Invalid JSON is rejected.无效的JSON会被拒绝。

CREATE TABLE t1 (c1 INT ENGINE_ATTRIBUTE='{"key":"value"}');

ENGINE_ATTRIBUTE and SECONDARY_ENGINE_ATTRIBUTE values can be repeated without error. ENGINE_ATTRIBUTE和SECONDARY_ENGINE_ATTRIBUTE值可以无错误地重复。In this case, the last specified value is used.在这种情况下，将使用最后指定的值。

ENGINE_ATTRIBUTE and SECONDARY_ENGINE_ATTRIBUTE values are not checked by the server, nor are they cleared when the table's storage engine is changed.服务器不会检查ENGINE_ATTRIBUTE性和SECONDARY_ENGINE_ATTRIBUTE值，也不会在更改表的存储引擎时清除它们。

STORAGE

For NDB tables, it is possible to specify whether the column is stored on disk or in memory by using a STORAGE clause. 对于NDB表，可以使用存储子句指定列是存储在磁盘上还是存储在内存中。STORAGE DISK causes the column to be stored on disk, and STORAGE MEMORY causes in-memory storage to be used. STORAGE DISK导致列存储在磁盘上，而STORAGE MEMORY导致使用内存内存储。The CREATE TABLE statement used must still include a TABLESPACE clause:使用的CREATE TABLE语句必须仍然包含TABLESPACE子句：

mysql> CREATE TABLE t1 (
    ->     c1 INT STORAGE DISK,
    ->     c2 INT STORAGE MEMORY
    -> ) ENGINE NDB;
ERROR 1005 (HY000): Can't create table 'c.t1' (errno: 140)

mysql> CREATE TABLE t1 (
    ->     c1 INT STORAGE DISK,
    ->     c2 INT STORAGE MEMORY
    -> ) TABLESPACE ts_1 ENGINE NDB;
Query OK, 0 rows affected (1.06 sec)

For NDB tables, STORAGE DEFAULT is equivalent to STORAGE MEMORY.对于NDB表，STORAGE DEFAULT相当于STORAGE MEMORY。

The STORAGE clause has no effect on tables using storage engines other than NDB. STORAGE子句对使用除NDB以外的存储引擎的表没有影响。The STORAGE keyword is supported only in the build of mysqld that is supplied with NDB Cluster; it is not recognized in any other version of MySQL, where any attempt to use the STORAGE keyword causes a syntax error.STORAGE关键字仅在NDB 群集提供的mysqld构建中受支持；它在任何其他版本的MySQL中都无法识别，任何使用STORAGE关键字的尝试都会导致语法错误。

GENERATED ALWAYS

Used to specify a generated column expression. 用于指定生成的列表达式。For information about generated columns, see Section 13.1.20.8, “CREATE TABLE and Generated Columns”.有关生成列的信息，请参阅第13.1.20.8节，“创建表和生成列”。

Stored generated columns can be indexed. 可以为存储的生成列编制索引。InnoDB supports secondary indexes on virtual generated columns. InnoDB支持虚拟生成列上的辅助索引。See Section 13.1.20.9, “Secondary Indexes and Generated Columns”.请参阅第13.1.20.9节，“二级索引和生成列”。

CONSTRAINT symbol

The CONSTRAINT symbol clause may be given to name a constraint. 可以使用CONSTRAINT symbol子句来命名约束。If the clause is not given, or a symbol is not included following the CONSTRAINT keyword, MySQL automatically generates a constraint name, with the exception noted below. 如果没有给出子句，或者CONSTRAINT关键字后面没有包含symbol，MySQL会自动生成一个约束名称，下面会指出一个例外。The symbol value, if used, must be unique per schema (database), per constraint type. 如果使用symbol值，则每个模式（数据库）和约束类型的符号值必须是唯一的。A duplicate symbol results in an error. 重复的symbol会导致错误。See also the discussion about length limits of generated constraint identifiers at Section 9.2.1, “Identifier Length Limits”.另见第9.2.1节，“标识符长度限制”中关于生成约束标识符长度限制的讨论。

The SQL standard specifies that all types of constraints (primary key, unique index, foreign key, check) belong to the same namespace. SQL标准指定所有类型的约束（主键、唯一索引、外键、检查）都属于同一名称空间。In MySQL, each constraint type has its own namespace per schema. 在MySQL中，每个约束类型在每个模式中都有自己的名称空间。Consequently, names for each type of constraint must be unique per schema, but constraints of different types can have the same name.因此，每种类型的约束的名称在每个模式中都必须是唯一的，但不同类型的约束可以具有相同的名称。

PRIMARY KEY

A unique index where all key columns must be defined as NOT NULL. 唯一索引，其中所有键列必须定义为NOT NULL。If they are not explicitly declared as NOT NULL, MySQL declares them so implicitly (and silently). 如果它们没有显式声明为NOT NULL，MySQL就会隐式地（静默地）声明它们。A table can have only one PRIMARY KEY. 一个表只能有一个主键。The name of a PRIMARY KEY is always PRIMARY, which thus cannot be used as the name for any other kind of index.主键的名称始终是PRIMARY，因此不能用作任何其他类型索引的名称。

If you do not have a PRIMARY KEY and an application asks for the PRIMARY KEY in your tables, MySQL returns the first UNIQUE index that has no NULL columns as the PRIMARY KEY.如果您没有主键，并且应用程序在表中请求主键，MySQL将返回第一个不包含NULL列的UNIQUE索引作为主键。

In InnoDB tables, keep the PRIMARY KEY short to minimize storage overhead for secondary indexes. 在InnoDB表中，请保持PRIMARY KEY简短，以最大限度地减少辅助索引的存储开销。Each secondary index entry contains a copy of the primary key columns for the corresponding row. 每个辅助索引项都包含对应行的主键列的副本。(See Section 15.6.2.1, “Clustered and Secondary Indexes”.)（请参阅第15.6.2.1节，“聚集索引和二级索引”。）

In the created table, a PRIMARY KEY is placed first, followed by all UNIQUE indexes, and then the nonunique indexes. 在创建的表中，首先放置PRIMARY KEY，然后是所有UNIQUE索引，然后是非唯一索引。This helps the MySQL optimizer to prioritize which index to use and also more quickly to detect duplicated UNIQUE keys.这有助于MySQL优化器确定要使用的索引的优先级，并更快地检测重复的UNIQUE键。

A PRIMARY KEY can be a multiple-column index. PRIMARY KEY可以是多列索引。However, you cannot create a multiple-column index using the PRIMARY KEY key attribute in a column specification. 但是，不能使用列规范中的PRIMARY KEY属性创建多列索引。Doing so only marks that single column as primary. 这样做只会将单个列标记为主列。You must use a separate PRIMARY KEY(key_part, ...) clause.您必须使用单独的主键PRIMARY KEY(key_part, ...)子句。

If a table has a PRIMARY KEY or UNIQUE NOT NULL index that consists of a single column that has an integer type, you can use _rowid to refer to the indexed column in SELECT statements, as described in Unique Indexes.如果表的PRIMARY KEY或UNIQUE NOT NULL索引由一个整型列组成，则可以使用_rowid在SELECT语句中引用索引列，如唯一索引中所述。

In MySQL, the name of a PRIMARY KEY is PRIMARY. 在MySQL中，PRIMARY KEY的名称是PRIMARY。For other indexes, if you do not assign a name, the index is assigned the same name as the first indexed column, with an optional suffix (_2, _3, ...) to make it unique. 对于其他索引，如果未指定名称，则将为索引指定与第一个索引列相同的名称，并使用可选后缀（_2、_3、…）使其唯一。You can see index names for a table using SHOW INDEX FROM tbl_name. 您可以使用SHOW INDEX FROM tbl_name查看表的索引名。See Section 13.7.7.22, “SHOW INDEX Statement”.请参阅第13.7.7.22节，“显示索引报表”。

KEY | INDEX

KEY is normally a synonym for INDEX. KEY通常是INDEX的同义词。The key attribute PRIMARY KEY can also be specified as just KEY when given in a column definition. 在列定义中给定键属性PRIMARY KEY时，也可以将其指定为仅KEY。This was implemented for compatibility with other database systems.这是为了与其他数据库系统兼容而实现的。

UNIQUE

A UNIQUE index creates a constraint such that all values in the index must be distinct. UNIQUE索引会创建一个约束，使得索引中的所有值都必须是不同的。An error occurs if you try to add a new row with a key value that matches an existing row. 如果尝试添加键值与现有行匹配的新行，则会发生错误。For all engines, a UNIQUE index permits multiple NULL values for columns that can contain NULL. 对于所有引擎，UNIQUE索引允许包含NULL的列具有多个NULL值。If you specify a prefix value for a column in a UNIQUE index, the column values must be unique within the prefix length.如果为UNIQUE索引中的列指定前缀值，则列值在前缀长度内必须唯一。

If a table has a PRIMARY KEY or UNIQUE NOT NULL index that consists of a single column that has an integer type, you can use _rowid to refer to the indexed column in SELECT statements, as described in Unique Indexes.如果表的PRIMARY KEY或UNIQUE NOT NULL索引由一个整型列组成，则可以使用_rowid在SELECT语句中引用索引列，如唯一索引中所述。

FULLTEXT

A FULLTEXT index is a special type of index used for full-text searches. FULLTEXT索引是用于全文搜索的一种特殊类型的索引。Only the InnoDB and MyISAM storage engines support FULLTEXT indexes. 只有InnoDB和MyISAM存储引擎支持全文索引。They can be created only from CHAR, VARCHAR, and TEXT columns. 它们只能从CHAR、VARCHAR和TEXT列创建。Indexing always happens over the entire column; column prefix indexing is not supported and any prefix length is ignored if specified. 索引总是发生在整个列上；不支持列前缀索引，如果指定，则忽略任何前缀长度。See Section 12.10, “Full-Text Search Functions”, for details of operation. 有关操作的详细信息，请参阅第12.10节，“全文搜索功能”。A WITH PARSER clause can be specified as an index_option value to associate a parser plugin with the index if full-text indexing and searching operations need special handling. 如果全文索引和搜索操作需要特殊处理，可以将WITH PARSER子句指定为index_option值，以将解析器插件与索引关联起来。This clause is valid only for FULLTEXT indexes. 此子句仅对FULLTEXT索引有效。InnoDB and MyISAM support full-text parser plugins. InnoDB和MyISAM支持全文解析器插件。See Full-Text Parser Plugins and Writing Full-Text Parser Plugins for more information.有关更多信息，请参阅全文解析器插件和编写全文解析器插件。

SPATIAL

You can create SPATIAL indexes on spatial data types. 可以在SPATIAL数据类型上创建空间索引。Spatial types are supported only for InnoDB and MyISAM tables, and indexed columns must be declared as NOT NULL. 仅InnoDB和MyISAM表支持空间类型，索引列必须声明为NOT NULL。See Section 11.4, “Spatial Data Types”.请参阅第11.4节，“空间数据类型”。

FOREIGN KEY

MySQL supports foreign keys, which let you cross-reference related data across tables, and foreign key constraints, which help keep this spread-out data consistent. MySQL支持外键（允许跨表交叉引用相关数据）和外键约束（有助于保持数据分布的一致性）。For definition and option information, see reference_definition, and reference_option.有关定义和选项信息，请参见reference_definition和reference_option。

Partitioned tables employing the InnoDB storage engine do not support foreign keys. 使用InnoDB存储引擎的分区表不支持外键。See Section 24.6, “Restrictions and Limitations on Partitioning”, for more information.有关更多信息，请参见第24.6节，“分区的约束和局限性”。

CHECK

The CHECK clause enables the creation of constraints to be checked for data values in table rows. CHECK子句允许为表行中的数据值检查约束的创建。See Section 13.1.20.6, “CHECK Constraints”.请参阅第13.1.20.6节，“检查约束”。

key_part

index_type

Some storage engines permit you to specify an index type when creating an index. 某些存储引擎允许您在创建索引时指定索引类型。The syntax for the index_type specifier is USING type_name.index_type说明符的语法是USING type_name。

Example:例子：

CREATE TABLE lookup
  (id INT, INDEX USING BTREE (id))
  ENGINE = MEMORY;

The preferred position for USING is after the index column list. 首选的USING位置是在索引列列表之后。It can be given before the column list, but support for use of the option in that position is deprecated and you should expect it to be removed in a future MySQL release.它可以在列列表之前给出，但是不推荐在该位置使用该选项，您应该期望在将来的MySQL版本中删除它。

index_option

index_option values specify additional options for an index.index_option值指定索引的其他选项。

For more information about permissible index_option values, see Section 13.1.15, “CREATE INDEX Statement”. 有关允许index_option值的更多信息，请参阅第13.1.15节，“创建索引语句”。For more information about indexes, see Section 8.3.1, “How MySQL Uses Indexes”.有关索引的更多信息，请参阅第8.3.1节，“MySQL如何使用索引”。

reference_definition

For reference_definition syntax details and examples, see Section 13.1.20.5, “FOREIGN KEY Constraints”.有关reference_definition语法的详细信息和示例，请参见第13.1.20.5节，“外键约束”。

InnoDB and NDB tables support checking of foreign key constraints. InnoDB和NDB表支持检查外键约束。The columns of the referenced table must always be explicitly named. 引用表的列必须始终显式命名。Both ON DELETE and ON UPDATE actions on foreign keys are supported. 支持外键上的ON DELETE和ON UPDATE操作。For more detailed information and examples, see Section 13.1.20.5, “FOREIGN KEY Constraints”.有关更多详细信息和示例，请参阅第13.1.20.5节，“外键约束”。

For other storage engines, MySQL Server parses and ignores the FOREIGN KEY and REFERENCES syntax in CREATE TABLE statements. 对于其他存储引擎，MySQL服务器解析并忽略CREATE TABLE语句中的FOREIGN KEY和REFERENCES语法。See Section 1.7.2.3, “FOREIGN KEY Constraint Differences”.请参阅第1.7.2.3节，“外键约束差异”。

reference_option

For information about the RESTRICT, CASCADE, SET NULL, NO ACTION, and SET DEFAULT options, see Section 13.1.20.5, “FOREIGN KEY Constraints”.有关RESTRICT（限制）、CASCADE（级联）、SET NULL、NO ACTION（无操作）和SET DEFAULT（设置默认）选项的信息，请参阅第13.1.20.5节，“外键约束”。

ENGINE

Specifies the storage engine for the table, using one of the names shown in the following table. 使用下表中显示的名称之一指定表的存储引擎。The engine name can be unquoted or quoted. 引擎名称可以是不带引号的，也可以是带引号的。The quoted name 'DEFAULT' is recognized but ignored.已识别引用的名称'DEFAULT'，但已忽略该名称。

By default, if a storage engine is specified that is not available, the statement fails with an error. 默认情况下，如果指定的存储引擎不可用，则该语句将失败并出错。You can override this behavior by removing NO_ENGINE_SUBSTITUTION from the server SQL mode (see Section 5.1.11, “Server SQL Modes”) so that MySQL allows substitution of the specified engine with the default storage engine instead. 您可以通过从服务器SQL模式（请参阅第5.1.11节，“服务器SQL模式”）中删除NO_ENGINE_SUBSTITUTION（无引擎替换）来覆盖此行为，以便MySQL允许使用默认存储引擎替换指定的引擎。Normally in such cases, this is InnoDB, which is the default value for the default_storage_engine system variable. 通常在这种情况下，这是InnoDB，它是default_storage_engine系统变量的默认值。When NO_ENGINE_SUBSTITUTION is disabled, a warning occurs if the storage engine specification is not honored.当NO_ENGINE_SUBSTITUTION被禁用的时候，如果不遵守存储引擎规范，将出现警告。

AUTOEXTEND_SIZE

Defines the amount by which InnoDB extends the size of the tablespace when it becomes full. 定义InnoDB在表空间满时扩展表空间大小的量。Introduced in MySQL 8.0.23. The setting must be a multiple of 4MB. 在MySQL 8.0.23中引入。该设置必须是4MB的倍数。The default setting is 0, which causes the tablespace to be extended according to the implicit default behavior. 默认设置为0，这将根据隐式默认行为扩展表空间。For more information, see Section 15.6.3.9, “Tablespace AUTOEXTEND_SIZE Configuration”.有关更多信息，请参阅第15.6.3.9节，“表空间自动扩展大小配置”。

AUTO_INCREMENT

The initial AUTO_INCREMENT value for the table. 表的初始AUTO_INCREMENT值。In MySQL 8.0, this works for MyISAM, MEMORY, InnoDB, and ARCHIVE tables. 在MySQL 8.0中，这适用于MyISAM、MEMORY、InnoDB和ARCHIVE表。To set the first auto-increment value for engines that do not support the AUTO_INCREMENT table option, insert a “dummy” row with a value one less than the desired value after creating the table, and then delete the dummy row.要为不支持AUTO_INCREMENT表选项的发动机设置第一个自动增量值，请在创建表后插入一个值小于所需值1的“虚拟”行，然后删除虚拟行。

For engines that support the AUTO_INCREMENT table option in CREATE TABLE statements, you can also use ALTER TABLE tbl_name AUTO_INCREMENT = N to reset the AUTO_INCREMENT value. 对于支持CREATE TABLE语句中的AUTO_INCREMENT表选项的引擎，还可以使用ALTER TABLE tbl_name AUTO_INCREMENT = N以重置AUTO_INCREMENT值。The value cannot be set lower than the maximum value currently in the column.该值不能设置为低于列中当前的最大值。

AVG_ROW_LENGTH

An approximation of the average row length for your table. 表的平均行长度的近似值。You need to set this only for large tables with variable-size rows.您只需要为具有可变大小行的大型表设置此选项。

When you create a MyISAM table, MySQL uses the product of the MAX_ROWS and AVG_ROW_LENGTH options to decide how big the resulting table is. 当您创建MyISAM表时，MySQL使用MAX_ROWS和AVG_ROW_LENGTH选项的乘积来决定结果表的大小。If you don't specify either option, the maximum size for MyISAM data and index files is 256TB by default. 如果不指定这两个选项，MyISAM数据和索引文件的最大大小默认为256TB。(If your operating system does not support files that large, table sizes are constrained by the file size limit.) （如果操作系统不支持如此大的文件，则表大小受文件大小限制的约束。）If you want to keep down the pointer sizes to make the index smaller and faster and you don't really need big files, you can decrease the default pointer size by setting the myisam_data_pointer_size system variable. 如果希望减小指针大小以使索引更小更快，并且实际上不需要大文件，可以通过设置myisam_data_pointer_size系统变量来减小默认指针大小。(See Section 5.1.8, “Server System Variables”.) （请参阅第5.1.8节“服务器系统变量”。）If you want all your tables to be able to grow above the default limit and are willing to have your tables slightly slower and larger than necessary, you can increase the default pointer size by setting this variable. 如果希望所有表的增长速度都能超过默认限制，并且希望表的速度稍微慢一些，并且比需要的稍大一些，则可以通过设置此变量来增加默认指针大小。Setting the value to 7 permits table sizes up to 65,536TB.将该值设置为7允许表格大小最大为65536TB。

[DEFAULT] CHARACTER SET

Specifies a default character set for the table. 指定表格的默认字符集。CHARSET is a synonym for CHARACTER SET. CHARSET是CHARACTER SET的同义词。If the character set name is DEFAULT, the database character set is used.如果字符集名称为DEFAULT，则使用数据库字符集。

CHECKSUM

Set this to 1 if you want MySQL to maintain a live checksum for all rows (that is, a checksum that MySQL updates automatically as the table changes). 如果希望MySQL为所有行维护实时校验和（即，MySQL在表更改时自动更新的校验和），请将其设置为1。This makes the table a little slower to update, but also makes it easier to find corrupted tables. 这使得表的更新速度稍慢，但也使查找损坏的表变得更容易。The CHECKSUM TABLE statement reports the checksum. CHECKSUM TABLE语句报告校验和。(MyISAM only.)（仅限MyISAM。）

[DEFAULT] COLLATE

Specifies a default collation for the table.指定表的默认排序规则。

COMMENT

A comment for the table, up to 2048 characters long.表的注释，最长2048个字符。

You can set the InnoDB MERGE_THRESHOLD value for a table using the table_option COMMENT clause. 可以使用table_option COMMENT子句为表设置InnoDB MERGE_THRESHOLD值。See Section 15.8.11, “Configuring the Merge Threshold for Index Pages”.请参阅第15.8.11节，“为索引页配置合并阈值”。

Setting NDB_TABLE options.设置NDB_表选项。  The table comment in a CREATE TABLE that creates an NDB table or an ALTER TABLE statement which alters one can also be used to specify one to four of the NDB_TABLE options NOLOGGING, READ_BACKUP, PARTITION_BALANCE, or FULLY_REPLICATED as a set of name-value pairs, separated by commas if need be, immediately following the string NDB_TABLE= that begins the quoted comment text. 创建NDB表的CREATE TABLE中的表注释或更改NDB表的ALTER TABLE语句也可用于指定一到四个NDB_TABLE选项NOLOGING、READ_BACKUP、PARTITION_BALANCE或FULLY_REPLICATED为一组名称-值对，必要时用逗号分隔，紧跟在字符串NDB_TABLE=之后，该字符串开始引用的注释文本。An example statement using this syntax is shown here (emphasized text):此处显示了使用此语法的示例语句（强调文本）：

CREATE TABLE t1 (
    c1 INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
    c2 VARCHAR(100),
    c3 VARCHAR(100) )
ENGINE=NDB
COMMENT="NDB_TABLE=READ_BACKUP=0,PARTITION_BALANCE=FOR_RP_BY_NODE";

Spaces are not permitted within the quoted string. 带引号的字符串中不允许有空格。The string is case-insensitive.字符串不区分大小写。

The comment is displayed as part of the ouput of SHOW CREATE TABLE. 注释显示为SHOW CREATE TABLE输出的一部分。The text of the comment is also available as the TABLE_COMMENT column of the MySQL Information Schema TABLES table.注释的文本也可以作为MySQL信息架构TABLES的TABLE_COMMENT列使用。

This comment syntax is also supported with ALTER TABLE statements for NDB tables. NDB表的ALTER TABLE语句也支持此注释语法。Keep in mind that a table comment used with ALTER TABLE replaces any existing comment which the table might have had perviously.请记住，与ALTER TABLE一起使用的表注释将替换表中可能存在的任何现有注释。

Setting the MERGE_THRESHOLD option in table comments is not supported for NDB tables (it is ignored).NDB表不支持在表注释中设置MERGE_THRESHOLD选项（忽略该选项）。

For complete syntax information and examples, see Section 13.1.20.11, “Setting NDB_TABLE Options”.有关完整的语法信息和示例，请参阅第13.1.20.11节，“设置NDB_TABLE选项”。

COMPRESSION

The compression algorithm used for page level compression for InnoDB tables. 用于InnoDB表的页面级压缩的压缩算法。Supported values include Zlib, LZ4, and None. 支持的值包括Zlib、LZ4和None。The COMPRESSION attribute was introduced with the transparent page compression feature. COMPRESSION属性是通过透明页面压缩特性引入的。Page compression is only supported with InnoDB tables that reside in file-per-table tablespaces, and is only available on Linux and Windows platforms that support sparse files and hole punching. 页面压缩仅支持驻留在每个表的文件表空间中的InnoDB表，并且仅在支持稀疏文件和打孔的Linux和Windows平台上可用。For more information, see Section 15.9.2, “InnoDB Page Compression”.有关更多信息，请参阅第15.9.2节，“InnoDB页面压缩”。

CONNECTION

The connection string for a FEDERATED table.FEDERATED（联合）表的连接字符串。

DATA DIRECTORY, INDEX DIRECTORY

For InnoDB, the DATA DIRECTORY='directory' clause permits creating tables outside of the data directory. 对于InnoDB，DATA DIRECTORY='directory'子句允许在数据目录之外创建表。The innodb_file_per_table variable must be enabled to use the DATA DIRECTORY clause. The full directory path must be specified. 必须启用innodb_file_per_table变量才能使用DATA DIRECTORY子句。必须指定完整的目录路径。As of MySQL 8.0.21, the directory specified must be known to InnoDB. 从MySQL 8.0.21开始，InnoDB必须知道指定的目录。For more information, see Section 15.6.1.2, “Creating Tables Externally”.有关更多信息，请参阅第15.6.1.2节，“外部创建表”。

When creating MyISAM tables, you can use the DATA DIRECTORY='directory' clause, the INDEX DIRECTORY='directory' clause, or both. 创建MyISAM表时，可以使用DATA DIRECTORY='directory'子句、INDEX DIRECTORY='directory'子句或两者兼用。They specify where to put a MyISAM table's data file and index file, respectively. 它们分别指定MyISAM表的数据文件和索引文件的放置位置。Unlike InnoDB tables, MySQL does not create subdirectories that correspond to the database name when creating a MyISAM table with a DATA DIRECTORY or INDEX DIRECTORY option. 与InnoDB表不同，在使用DATA DIRECTORY选项或INDEX DIRECTORY选项创建MyISAM表时，MySQL不会创建与数据库名称对应的子目录。Files are created in the directory that is specified.在指定的目录中创建文件。

You must have the FILE privilege to use the DATA DIRECTORY or INDEX DIRECTORY table option.您必须具有FILE权限才能使用DATA DIRECTORY表选项或INDEX DIRECTORY表选项。

These options work only when you are not using the --skip-symbolic-links option. 这些选项仅在不使用--skip-symbolic-links选项时有效。Your operating system must also have a working, thread-safe realpath() call. 您的操作系统还必须有一个线程安全的realpath()调用。See Section 8.12.2.2, “Using Symbolic Links for MyISAM Tables on Unix”, for more complete information.有关更多完整信息，请参阅第8.12.2.2节，“在Unix上为MyISAM表使用符号链接”。

If a MyISAM table is created with no DATA DIRECTORY option, the .MYD file is created in the database directory. 如果创建MyISAM表时没有DATA DIRECTORY选项，则会在数据库目录中创建.MYD文件。By default, if MyISAM finds an existing .MYD file in this case, it overwrites it. 默认情况下，如果MyISAM在本例中找到现有的.MYD文件，它将覆盖该文件。The same applies to .MYI files for tables created with no INDEX DIRECTORY option. 这同样适用于不使用索引目录选项创建的表的.MYI文件。To suppress this behavior, start the server with the --keep_files_on_create option, in which case MyISAM does not overwrite existing files and returns an error instead.要抑制此行为，请使用--keep_files_on_create选项启动服务器，在这种情况下，MyISAM不会覆盖现有文件，而是返回一个错误。

If a MyISAM table is created with a DATA DIRECTORY or INDEX DIRECTORY option and an existing .MYD or .MYI file is found, MyISAM always returns an error, and does not overwrite a file in the specified directory.如果使用DATA DIRECTORY或INDEX DIRECTORY选项创建MyISAM表，并且找到现有的.MYD或.MYI文件，则MyISAM始终返回错误，并且不会覆盖指定目录中的文件。

DELAY_KEY_WRITE

Set this to 1 if you want to delay key updates for the table until the table is closed. 如果要延迟表的键更新直到关闭表，请将此设置为1。See the description of the delay_key_write system variable in Section 5.1.8, “Server System Variables”. 请参阅第5.1.8节，“服务器系统变量”中对delay_key_write系统变量的描述。(MyISAM only.)

ENCRYPTION

The ENCRYPTION clause enables or disables page-level data encryption for an InnoDB table. ENCRYPTION子句启用或禁用InnoDB表的页面级数据加密。A keyring plugin must be installed and configured before encryption can be enabled. 在启用加密之前，必须安装并配置密钥环插件。Prior to MySQL 8.0.16, the ENCRYPTION clause can only be specified when creating a table in an a file-per-table tablespace. 在MySQL 8.0.16之前，只有在每个表空间的文件中创建表时才能指定ENCRYPTION子句。As of MySQL 8.0.16, the ENCRYPTION clause can also be specified when creating a table in a general tablespace.从MySQL 8.0.16开始，在常规表空间中创建表时也可以指定ENCRYPTION子句。

As of MySQL 8.0.16, a table inherits the default schema encryption if an ENCRYPTION clause is not specified. 从MySQL 8.0.16开始，如果未指定ENCRYPTION子句，表将继承默认模式加密。If the table_encryption_privilege_check variable is enabled, the TABLE_ENCRYPTION_ADMIN privilege is required to create a table with an ENCRYPTION clause setting that differs from the default schema encryption. 如果启用了table_encryption_privilege_check变量，则需要TABLE_ENCRYPTION_ADMIN权限来创建具有不同于默认架构加密的ENCRYPTION子句设置的表。When creating a table in a general tablespace, table and tablespace encryption must match.在常规表空间中创建表时，表和表空间加密必须匹配。

As of MySQL 8.0.16, specifying an ENCRYPTION clause with a value other than 'N' or '' is not permitted when using a storage engine that does not support encryption. 从MySQL 8.0.16开始，在使用不支持加密的存储引擎时，不允许使用'N'或''以外的值指定ENCRYPTION子句。Previously, the clause was accepted.此前，该子句被接受。

For more information, see Section 15.13, “InnoDB Data-at-Rest Encryption”.有关更多信息，请参阅第15.13节，“InnoDB静态数据加密”。

ENGINE_ATTRIBUTE and SECONDARY_ENGINE_ATTRIBUTE options (available as of MySQL 8.0.21) are used to specify table attributes for primary and secondary storage engines. ENGINE_ATTRIBUTE选项和SECONDARY_ENGINE_ATTRIBUTE选项（从MySQL 8.0.21开始提供）用于指定主存储引擎和辅助存储引擎的表属性。The options are reserved for future use.这些选项保留供将来使用。

Permitted values are a string literal containing a valid JSON document or an empty string (''). 允许的值是包含有效JSON文档的字符串文字或空字符串（''）。Invalid JSON is rejected.无效的JSON被拒绝。

CREATE TABLE t1 (c1 INT) ENGINE_ATTRIBUTE='{"key":"value"}';

ENGINE_ATTRIBUTE and SECONDARY_ENGINE_ATTRIBUTE values can be repeated without error. ENGINE_ATTRIBUTE值和SECONDARY_ENGINE_ATTRIBUTE值可以无错误地重复。In this case, the last specified value is used.在这种情况下，将使用最后指定的值。

ENGINE_ATTRIBUTE and SECONDARY_ENGINE_ATTRIBUTE values are not checked by the server, nor are they cleared when the table's storage engine is changed.服务器不会检查ENGINE_ATTRIBUTE和SECONDARY_ENGINE_ATTRIBUTE值，也不会在更改表的存储引擎时清除它们。

INSERT_METHOD

If you want to insert data into a MERGE table, you must specify with INSERT_METHOD the table into which the row should be inserted. 如果要将数据插入MERGE表，必须使用INSERT_METHOD指定应将行插入的表。INSERT_METHOD is an option useful for MERGE tables only. INSERT_METHOD仅对MERGE表有用。Use a value of FIRST or LAST to have inserts go to the first or last table, or a value of NO to prevent inserts. 使用值FIRST或LAST可使插入转到第一个或最后一个表，或使用值NO可防止插入。See Section 16.7, “The MERGE Storage Engine”.请参阅第16.7节，“合并存储引擎”。

KEY_BLOCK_SIZE

For MyISAM tables, KEY_BLOCK_SIZE optionally specifies the size in bytes to use for index key blocks. 对于MyISAM表，KEY_BLOCK_SIZE可以选择指定索引键块使用的大小（以字节为单位）。The value is treated as a hint; a different size could be used if necessary. 该值被视为提示；如有必要，可使用不同的尺寸。A KEY_BLOCK_SIZE value specified for an individual index definition overrides the table-level KEY_BLOCK_SIZE value.为单个索引定义指定的KEY_BLOCK_SIZE值覆盖表级KEY_BLOCK_SIZE值。

For InnoDB tables, KEY_BLOCK_SIZE specifies the page size in kilobytes to use for compressed InnoDB tables. 对于InnoDB表，KEY_BLOCK_SIZE指定用于压缩InnoDB表的页面大小（以KB为单位）。The KEY_BLOCK_SIZE value is treated as a hint; a different size could be used by InnoDB if necessary. KEY_BLOCK_SIZE值被视为提示；如果需要，InnoDB可以使用不同的大小。KEY_BLOCK_SIZE can only be less than or equal to the innodb_page_size value. KEY_BLOCK_SIZE只能小于或等于InnoDB页面大小值。A value of 0 represents the default compressed page size, which is half of the innodb_page_size value. 值0表示默认的压缩页面大小，它是innodb_page_size值的一半。Depending on innodb_page_size, possible KEY_BLOCK_SIZE values include 0, 1, 2, 4, 8, and 16. 根据innodb_page_size，可能的KEY_BLOCK_SIZE值包括0、1、2、4、8和16。See Section 15.9.1, “InnoDB Table Compression” for more information.有关更多信息，请参阅第15.9.1节，“InnoDB表压缩”。

Oracle recommends enabling innodb_strict_mode when specifying KEY_BLOCK_SIZE for InnoDB tables. Oracle建议在为InnoDB表指定KEY_BLOCK_SIZE时启用innodb_strict_mode。When innodb_strict_mode is enabled, specifying an invalid KEY_BLOCK_SIZE value returns an error. 启用innodb_strict_mode时，指定无效的KEY_BLOCK_SIZE<值将返回错误。If innodb_strict_mode is disabled, an invalid KEY_BLOCK_SIZE value results in a warning, and the KEY_BLOCK_SIZE option is ignored.如果禁用innodb_strict_mode，则无效的KEY_BLOCK_SIZE值将导致警告，并且忽略KEY_BLOCK_SIZE选项。

The Create_options column in response to SHOW TABLE STATUS reports the actual KEY_BLOCK_SIZE used by the table, as does SHOW CREATE TABLE.响应SHOW TABLE STATUS（显示表格状态）的Create_options（创建选项）列报告表格使用的实际键块大小，SHOW Create TABLE（显示创建表格）也是如此。

InnoDB only supports KEY_BLOCK_SIZE at the table level.InnoDB仅支持表级别的KEY_BLOCK_SIZE。

KEY_BLOCK_SIZE is not supported with 32KB and 64KB innodb_page_size values. 32KB和64KB innodb_page_size值不支持KEY_BLOCK_SIZE。InnoDB table compression does not support these pages sizes.InnoDB表压缩不支持这些页面大小。

InnoDB does not support the KEY_BLOCK_SIZE option when creating temporary tables.在创建临时表时，InnoDB不支持KEY_BLOCK_SIZE选项。

MAX_ROWS

The maximum number of rows you plan to store in the table. 计划在表中存储的最大行数。This is not a hard limit, but rather a hint to the storage engine that the table must be able to store at least this many rows.这不是一个硬限制，而是一个提示，提示存储引擎表必须能够存储至少这么多行。

The NDB storage engine treats this value as a maximum. NDB存储引擎将此值视为最大值。If you plan to create very large NDB Cluster tables (containing millions of rows), you should use this option to insure that NDB allocates sufficient number of index slots in the hash table used for storing hashes of the table's primary keys by setting MAX_ROWS = 2 * rows, where rows is the number of rows that you expect to insert into the table.如果计划创建非常大的NDB集群表（包含数百万行），则应使用此选项确保NDB在哈希表中分配足够数量的索引槽，用于通过设置MAX_ROWS = 2 * rows存储表主键的哈希，其中rows是希望插入表中的行数。

The maximum MAX_ROWS value is 4294967295; larger values are truncated to this limit.MAX_ROW的上限值为4294967295；较大的值将被截断到此限制。

MIN_ROWS

The minimum number of rows you plan to store in the table. 计划存储在表中的最小行数。The MEMORY storage engine uses this option as a hint about memory use.MEMORY存储引擎使用此选项作为内存使用的提示。

PACK_KEYS

Takes effect only with MyISAM tables. 仅对MyISAM表生效。Set this option to 1 if you want to have smaller indexes. 如果希望索引更小，请将此选项设置为1。This usually makes updates slower and reads faster. 这通常会使更新速度变慢，读取速度变快。Setting the option to 0 disables all packing of keys. 将选项设置为0将禁用所有密钥打包。Setting it to DEFAULT tells the storage engine to pack only long CHAR, VARCHAR, BINARY, or VARBINARY columns.将其设置为DEFAULT会告诉存储引擎仅打包长CHAR、VARCHAR、BINARY或VARBINARY列。

If you do not use PACK_KEYS, the default is to pack strings, but not numbers. 如果不使用PACK_KEYS，默认情况下会打包字符串，但不会打包数字。If you use PACK_KEYS=1, numbers are packed as well.如果使用PACK_key=1，则数字也会被打包。

When packing binary number keys, MySQL uses prefix compression:打包二进制数字键时，MySQL使用前缀压缩：

This means that if you have many equal keys on two consecutive rows, all following “same” keys usually only take two bytes (including the pointer to the row). 这意味着，如果在两个连续的行上有许多相等的键，那么后面的所有“相同”键通常只占用两个字节（包括指向该行的指针）。Compare this to the ordinary case where the following keys takes storage_size_for_key + pointer_size (where the pointer size is usually 4). 将此情况与普通情况进行比较，在普通情况下，以下键取用storage_size_for_key + pointer_size（其中指针大小通常为4）。Conversely, you get a significant benefit from prefix compression only if you have many numbers that are the same. 相反，只有当您有许多相同的数字时，前缀压缩才能带来显著的好处。If all keys are totally different, you use one byte more per key, if the key is not a key that can have NULL values. 如果所有键都完全不同，则每个键多使用一个字节，前提是该键不是可以具有NULL值的键。(In this case, the packed key length is stored in the same byte that is used to mark if a key is NULL.)（在这种情况下，压缩密钥长度存储在用于标记密钥是否为NULL的相同字节中。）

PASSWORD

This option is unused.此选项未使用。

ROW_FORMAT

Defines the physical format in which the rows are stored.定义存储行的物理格式。

When creating a table with strict mode disabled, the storage engine's default row format is used if the specified row format is not supported. 创建禁用严格模式的表时，如果不支持指定的行格式，则使用存储引擎的默认行格式。The actual row format of the table is reported in the Row_format column in response to SHOW TABLE STATUS. 表的实际行格式在Row_format列中报告，以响应SHOW TABLE STATUS。The Create_options column shows the row format that was specified in the CREATE TABLE statement, as does SHOW CREATE TABLE.Create_options列显示CREATE TABLE语句中指定的行格式，如SHOW CREATE TABLE。

Row format choices differ depending on the storage engine used for the table.行格式选择因用于表的存储引擎而异。

For InnoDB tables:对于InnoDB表：

For MyISAM tables, the option value can be FIXED or DYNAMIC for static or variable-length row format. 对于MyISAM表，对于静态或可变长度行格式，选项值可以是FIXED，也可以是DYNAMIC。myisampack sets the type to COMPRESSED. myisampack将类型设置为COMPRESSED。See Section 16.2.3, “MyISAM Table Storage Formats”.请参阅第16.2.3节，“MyISAM表格存储格式”。

For NDB tables, the default ROW_FORMAT is DYNAMIC.对于NDB表，默认的是DYNAMIC。

STATS_AUTO_RECALC

Specifies whether to automatically recalculate persistent statistics for an InnoDB table. 指定是否自动重新计算InnoDB表的持久统计信息。The value DEFAULT causes the persistent statistics setting for the table to be determined by the innodb_stats_auto_recalc configuration option. 默认值导致表的持久统计设置由innodb_stats_auto_recalc配置选项确定。The value 1 causes statistics to be recalculated when 10% of the data in the table has changed. 当表中10%的数据发生更改时，值1会导致重新计算统计信息。The value 0 prevents automatic recalculation for this table; with this setting, issue an ANALYZE TABLE statement to recalculate the statistics after making substantial changes to the table. 值0防止自动重新计算此表；使用此设置，在对表进行重大更改后，发出ANALYZE TABLE语句以重新计算统计信息。For more information about the persistent statistics feature, see Section 15.8.10.1, “Configuring Persistent Optimizer Statistics Parameters”.有关持久性统计特性的更多信息，请参阅第15.8.10.1节，“配置持久性优化器统计参数”。

STATS_PERSISTENT

Specifies whether to enable persistent statistics for an InnoDB table. 指定是否为InnoDB表启用持久统计信息。The value DEFAULT causes the persistent statistics setting for the table to be determined by the innodb_stats_persistent configuration option. DEFAULT值导致表的持久统计设置由innodb_stats_persistent配置选项确定。The value 1 enables persistent statistics for the table, while the value 0 turns off this feature. 值1启用表的持久统计信息，而值0禁用此功能。After enabling persistent statistics through a CREATE TABLE or ALTER TABLE statement, issue an ANALYZE TABLE statement to calculate the statistics, after loading representative data into the table. 通过CREATE TABLE或ALTER TABLE语句启用持久统计信息后，在将代表性数据加载到表中后，发出ANALYZE TABLE语句以计算统计信息。For more information about the persistent statistics feature, see Section 15.8.10.1, “Configuring Persistent Optimizer Statistics Parameters”.有关持久性统计特性的更多信息，请参阅第15.8.10.1节，“配置持久性优化器统计参数”。

STATS_SAMPLE_PAGES

The number of index pages to sample when estimating cardinality and other statistics for an indexed column, such as those calculated by ANALYZE TABLE. 在估计索引列的基数和其他统计信息（如由ANALYZE TABLE计算的统计信息）时要采样的索引页数。For more information, see Section 15.8.10.1, “Configuring Persistent Optimizer Statistics Parameters”.有关更多信息，请参阅第15.8.10.1节，“配置持久优化器统计参数”。

TABLESPACE

The TABLESPACE clause can be used to create a table in an existing general tablespace, a file-per-table tablespace, or the system tablespace.TABLESPACE子句可用于在现有常规表空间、每个表的文件表空间或系统表空间中创建表。

CREATE TABLE tbl_name ... TABLESPACE [=] tablespace_name

The general tablespace that you specify must exist prior to using the TABLESPACE clause. 在使用TABLESPACE子句之前，指定的常规表空间必须存在。For information about general tablespaces, see Section 15.6.3.3, “General Tablespaces”.有关常规表空间的信息，请参阅第15.6.3.3节，“常规表空间”。

The tablespace_name is a case-sensitive identifier. tablespace_name是区分大小写的标识符。It may be quoted or unquoted. 它可以是带引号的，也可以是不带引号的。The forward slash character (“/”) is not permitted. 不允许使用正斜杠字符（“/”）。Names beginning with “innodb_” are reserved for special use.以“innodb_”开头的名称保留供特殊使用。

To create a table in the system tablespace, specify innodb_system as the tablespace name.要在系统表空间中创建表，请指定innodb_system作为表空间名称。

CREATE TABLE tbl_name ... TABLESPACE [=] innodb_system

Using TABLESPACE [=] innodb_system, you can place a table of any uncompressed row format in the system tablespace regardless of the innodb_file_per_table setting. 使用TABLESPACE [=] innodb_system，您可以在系统表空间中放置任何未压缩行格式的表，而无需考虑innodb_file_per_table设置。For example, you can add a table with ROW_FORMAT=DYNAMIC to the system tablespace using TABLESPACE [=] innodb_system.例如，可以使用TABLESPACE [=] innodb_system将ROW_FORMAT=DYNAMIC的表添加到系统表空间。

To create a table in a file-per-table tablespace, specify innodb_file_per_table as the tablespace name.要在每个表空间的文件中创建表，请指定innodb_file_per_table作为表空间名称。

CREATE TABLE tbl_name ... TABLESPACE [=] innodb_file_per_table

The DATA DIRECTORY clause is permitted with CREATE TABLE ... TABLESPACE=innodb_file_per_table but is otherwise not supported for use in combination with the TABLESPACE clause. DATA DIRECTORY子句允许与CREATE TABLE ... TABLESPACE=innodb_file_per_table结合使用，但不支持与TABLESPACE子句结合使用。As of MySQL 8.0.21, the directory specified in a DATA DIRECTORY clause must be known to InnoDB. 从MySQL 8.0.21开始，InnoDB必须知道DATA DIRECTORY子句中指定的目录。For more information, see Using the DATA DIRECTORY Clause.有关更多信息，请参阅使用DATA DIRECTORY子句。

The STORAGE table option is employed only with NDB tables. STORAGE表选项仅用于NDB表。STORAGE determines the type of storage used (disk or memory), and can be either DISK or MEMORY.STORAGE决定使用的存储类型（磁盘或内存），可以是DISK或MEMORY。

TABLESPACE ... STORAGE DISK assigns a table to an NDB Cluster Disk Data tablespace. TABLESPACE ... STORAGE DISK将表分配给NDB群集磁盘数据表空间。The tablespace must already have been created using CREATE TABLESPACE. 表空间必须已经使用CREATE TABLESPACE创建。See Section 23.5.10, “NDB Cluster Disk Data Tables”, for more information.有关更多信息，请参阅第23.5.10节，“NDB群集磁盘数据表”。

UNION

Used to access a collection of identical MyISAM tables as one. 用于作为一个表访问相同MyISAM表的集合。This works only with MERGE tables. 这仅适用于MERGE表。See Section 16.7, “The MERGE Storage Engine”.请参阅第16.7节，“合并存储引擎”。

You must have SELECT, UPDATE, and DELETE privileges for the tables you map to a MERGE table.对于映射到MERGE表的表，您必须具有SELECT、UPDATE和DELETE权限。

PARTITION BY

If used, a partition_options clause begins with PARTITION BY. 如果使用，partition_options子句以PARTITION BY开头。This clause contains the function that is used to determine the partition; the function returns an integer value ranging from 1 to num, where num is the number of partitions. 此子句包含用于确定分区的函数；该函数返回一个从1到num的整数值，其中num是分区数。(The maximum number of user-defined partitions which a table may contain is 1024; the number of subpartitions—discussed later in this section—is included in this maximum.)（一个表可以包含的用户定义分区的最大数量为1024；本节后面讨论的子分区数量包含在该最大值中。）

HASH(expr)

Hashes one or more columns to create a key for placing and locating rows. 散列一个或多个列以创建用于放置和定位行的键。expr is an expression using one or more table columns. expr是使用一个或多个表列的表达式。This can be any valid MySQL expression (including MySQL functions) that yields a single integer value. 这可以是任何生成单个整数值的有效MySQL表达式（包括MySQL函数）。For example, these are both valid CREATE TABLE statements using PARTITION BY HASH:例如，这两条语句都是使用PARTITION BY HASH的有效CREATE TABLE语句：

CREATE TABLE t1 (col1 INT, col2 CHAR(5))
    PARTITION BY HASH(col1);

CREATE TABLE t1 (col1 INT, col2 CHAR(5), col3 DATETIME)
    PARTITION BY HASH ( YEAR(col3) );

You may not use either VALUES LESS THAN or VALUES IN clauses with PARTITION BY HASH.您不能使用VALUES LESS THAN子句或VALUES IN子句配合PARTITION BY HASH。

PARTITION BY HASH uses the remainder of expr divided by the number of partitions (that is, the modulus). PARTITION BY HASH使用expr的剩余部分除以分区数（即模数）。For examples and additional information, see Section 24.2.4, “HASH Partitioning”.有关示例和其他信息，请参阅第24.2.4节，“哈希分区”。

The LINEAR keyword entails a somewhat different algorithm. LINEAR关键字需要一个稍微不同的算法。In this case, the number of the partition in which a row is stored is calculated as the result of one or more logical AND operations. 在这种情况下，作为一个或多个逻辑AND操作的结果，计算存储行的分区数。For discussion and examples of linear hashing, see Section 24.2.4.1, “LINEAR HASH Partitioning”.有关线性哈希的讨论和示例，请参阅第24.2.4.1节，“线性哈希分区”。

KEY(column_list)

This is similar to HASH, except that MySQL supplies the hashing function so as to guarantee an even data distribution. 这类似于HASH，只是MySQL提供了散列函数以保证数据分布均匀。The column_list argument is simply a list of 1 or more table columns (maximum: 16). column_list参数只是一个包含1个或多个表列的列表（最大值：16）。This example shows a simple table partitioned by key, with 4 partitions:此示例显示了一个按键分区的简单表，共有4个分区：

CREATE TABLE tk (col1 INT, col2 CHAR(5), col3 DATE)
    PARTITION BY KEY(col3)
    PARTITIONS 4;

For tables that are partitioned by key, you can employ linear partitioning by using the LINEAR keyword. 对于按键分区的表，可以通过使用LINEAR关键字采用线性分区。This has the same effect as with tables that are partitioned by HASH. 这与使用HASH分区的表具有相同的效果。That is, the partition number is found using the & operator rather than the modulus (see Section 24.2.4.1, “LINEAR HASH Partitioning”, and Section 24.2.5, “KEY Partitioning”, for details). 也就是说，分区号是使用&运算符而不是模数（有关详细信息，请参阅第24.2.4.1节，“线性哈希分区”和第24.2.5节，“键分区”）。This example uses linear partitioning by key to distribute data between 5 partitions:此示例使用按键的线性分区在5个分区之间分配数据：

CREATE TABLE tk (col1 INT, col2 CHAR(5), col3 DATE)
    PARTITION BY LINEAR KEY(col3)
    PARTITIONS 5;

The ALGORITHM={1 | 2} option is supported with [SUB]PARTITION BY [LINEAR] KEY. 支持ALGORITHM={1 | 2}选项与[SUB]PARTITION BY [LINEAR] KEY配合使用。ALGORITHM=1 causes the server to use the same key-hashing functions as MySQL 5.1; ALGORITHM=2 means that the server employs the key-hashing functions implemented and used by default for new KEY partitioned tables in MySQL 5.5 and later. ALGORITHM=1导致服务器使用与MySQL 5.1相同的密钥散列函数；ALGORITHM=2意味着服务器使用默认情况下为MySQL 5.5及更高版本中的新KEY分区表实现和使用的密钥散列函数。(Partitioned tables created with the key-hashing functions employed in MySQL 5.5 and later cannot be used by a MySQL 5.1 server.) （使用MySQL 5.5及更高版本中使用的密钥散列函数创建的分区表不能由MySQL 5.1服务器使用。）Not specifying the option has the same effect as using ALGORITHM=2. 不指定该选项的效果与使用ALGORITHM=2的效果相同。This option is intended for use chiefly when upgrading or downgrading [LINEAR] KEY partitioned tables between MySQL 5.1 and later MySQL versions, or for creating tables partitioned by KEY or LINEAR KEY on a MySQL 5.5 or later server which can be used on a MySQL 5.1 server. 此选项主要用于在MySQL 5.1和更高版本的MySQL之间升级或降级[LINEAR] KEY分区表，或在MySQL 5.5或更高版本的服务器上创建可在MySQL 5.1服务器上使用的按键或线性键分区的表。For more information, see Section 13.1.9.1, “ALTER TABLE Partition Operations”.有关更多信息，请参阅第13.1.9.1节，“更改表分区操作”。

mysqldump in MySQL 5.7 (and later) writes this option encased in versioned comments, like this:MySQL 5.7（及更高版本）中的mysqldump将此选项封装在版本注释中，如下所示：

CREATE TABLE t1 (a INT)
/*!50100 PARTITION BY KEY */ /*!50611 ALGORITHM = 1 */ /*!50100 ()
      PARTITIONS 3 */

This causes MySQL 5.6.10 and earlier servers to ignore the option, which would otherwise cause a syntax error in those versions. 这会导致MySQL 5.6.10和更早版本的服务器忽略该选项，否则会在这些版本中导致语法错误。If you plan to load a dump made on a MySQL 5.7 server where you use tables that are partitioned or subpartitioned by KEY into a MySQL 5.6 server previous to version 5.6.11, be sure to consult Changes in MySQL 5.6, before proceeding. 如果您计划将MySQL 5.7服务器上的转储加载到5.6.11版本之前的MySQL 5.6服务器中，在该服务器上使用按KEY分区或子分区的表，请确保在继续之前查阅MySQL 5.6中的更改。(The information found there also applies if you are loading a dump containing KEY partitioned or subpartitioned tables made from a MySQL 5.7—actually 5.6.11 or later—server into a MySQL 5.5.30 or earlier server.)（如果您正在将包含从MySQL 5.7-5.6.11或更高版本服务器生成的KEY分区表或子分区表的转储加载到MySQL 5.5.30或更高版本服务器，则此处找到的信息也适用。）

Also in MySQL 5.6.11 and later, ALGORITHM=1 is shown when necessary in the output of SHOW CREATE TABLE using versioned comments in the same manner as mysqldump. 同样在MySQL 5.6.11及更高版本中，必要时，在SHOW CREATE TABLE的输出中使用版本化注释以与mysqldump相同的方式显示ALGORITHM=1。ALGORITHM=2 is always omitted from SHOW CREATE TABLE output, even if this option was specified when creating the original table.SHOW CREATE TABLE输出中始终忽略ALGORITHM=2，即使在创建原始表时指定了此选项。

You may not use either VALUES LESS THAN or VALUES IN clauses with PARTITION BY KEY.您不能将VALUES LESS THAN或VALUES IN子句与PARTITION BY KEY配合使用。

RANGE(expr)

In this case, expr shows a range of values using a set of VALUES LESS THAN operators. 在这种情况下，expr使用一组VALUES LESS THAN运算符的值来显示一系列值。When using range partitioning, you must define at least one partition using VALUES LESS THAN. 使用范围分区时，必须使用VALUES LESS THAN定义至少一个分区。You cannot use VALUES IN with range partitioning.不能将VALUES IN与范围分区配合使用。

Suppose that you have a table that you wish to partition on a column containing year values, according to the following scheme.假设您有一个表，希望根据以下方案在包含年份值的列上进行分区。

A table implementing such a partitioning scheme can be realized by the CREATE TABLE statement shown here:实现这种分区方案的表可以通过如下所示的CREATE TABLE语句来实现：

CREATE TABLE t1 (
    year_col  INT,
    some_data INT
)
PARTITION BY RANGE (year_col) (
    PARTITION p0 VALUES LESS THAN (1991),
    PARTITION p1 VALUES LESS THAN (1995),
    PARTITION p2 VALUES LESS THAN (1999),
    PARTITION p3 VALUES LESS THAN (2002),
    PARTITION p4 VALUES LESS THAN (2006),
    PARTITION p5 VALUES LESS THAN MAXVALUE
);

PARTITION ... VALUES LESS THAN ... statements work in a consecutive fashion. PARTITION ... VALUES LESS THAN ...语句以连续的方式工作。VALUES LESS THAN MAXVALUE works to specify “leftover” values that are greater than the maximum value otherwise specified.VALUES LESS THAN MAXVALUE用于指定大于其他指定的最大值的“剩余”值。

VALUES LESS THAN clauses work sequentially in a manner similar to that of the case portions of a switch ... case block (as found in many programming languages such as C, Java, and PHP). VALUES LESS THAN子句以类似于switch ... case块（在许多编程语言如C、Java和PHP中都可以找到）的case部分的方式顺序工作。That is, the clauses must be arranged in such a way that the upper limit specified in each successive VALUES LESS THAN is greater than that of the previous one, with the one referencing MAXVALUE coming last of all in the list.也就是说，子句的排列方式必须确保在每个连续值中指定的上限小于前一个值的上限，其中引用MAXVALUE的值位于列表中的最后一个值。

RANGE COLUMNS(column_list)

This variant on RANGE facilitates partition pruning for queries using range conditions on multiple columns (that is, having conditions such as WHERE a = 1 AND b < 10 or WHERE a = 1 AND b = 10 AND c < 10). 此RANGE变量有助于使用多列上的范围条件（即，具有诸如WHERE a = 1 AND b < 10或WHERE a = 1 AND b = 10 AND c < 10之类的条件）。It enables you to specify value ranges in multiple columns by using a list of columns in the COLUMNS clause and a set of column values in each PARTITION ... VALUES LESS THAN (value_list) partition definition clause. 它使您能够使用COLUMNS子句中的列列表和每个PARTITION ... VALUES LESS THAN (value_list)分区定义子句中的列值集来指定多列中的值范围。(In the simplest case, this set consists of a single column.) （在最简单的情况下，此集合由一列组成。）The maximum number of columns that can be referenced in the column_list and value_list is 16.column_list和value_list中可引用的最大列数为16。

The column_list used in the COLUMNS clause may contain only names of columns; each column in the list must be one of the following MySQL data types: the integer types; the string types; and time or date column types. COLUMNS子句中使用的column_list可能只包含列的名称；列表中的每一列必须是以下MySQL数据类型之一：整数类型；字符串类型；和时间或日期列类型。Columns using BLOB, TEXT, SET, ENUM, BIT, or spatial data types are not permitted; columns that use floating-point number types are also not permitted. 不允许使用BLOB、TEXT、SET、ENUM、BIT或空间数据类型的列；也不允许使用浮点数类型的列。You also may not use functions or arithmetic expressions in the COLUMNS clause.您也不能在COLUMNS子句中使用函数或算术表达式。

The VALUES LESS THAN clause used in a partition definition must specify a literal value for each column that appears in the COLUMNS() clause; that is, the list of values used for each VALUES LESS THAN clause must contain the same number of values as there are columns listed in the COLUMNS clause. 分区定义中使用的VALUES LESS THAN子句必须为COLUMNS()子句中出现的每一列指定一个文字值；也就是说，用于每个VALUES LESS THAN子句的值列表必须包含与COLUMNS子句中列出的列相同数目的值。An attempt to use more or fewer values in a VALUES LESS THAN clause than there are in the COLUMNS clause causes the statement to fail with the error Inconsistency in usage of column lists for partitioning.... 如果试图在VALUES LESS THAN子句中使用比COLUMNS子句中更多或更少的值，则会导致语句失败，因为分区列列表的使用不一致……。You cannot use NULL for any value appearing in VALUES LESS THAN. 对于VALUES LESS THAN中出现的任何值，不能使用NULL。It is possible to use MAXVALUE more than once for a given column other than the first, as shown in this example:对于给定列（第一列除外），可以多次使用MAXVALUE，如本例所示：

CREATE TABLE rc (
    a INT NOT NULL,
    b INT NOT NULL
)
PARTITION BY RANGE COLUMNS(a,b) (
    PARTITION p0 VALUES LESS THAN (10,5),
    PARTITION p1 VALUES LESS THAN (20,10),
    PARTITION p2 VALUES LESS THAN (50,MAXVALUE),
    PARTITION p3 VALUES LESS THAN (65,MAXVALUE),
    PARTITION p4 VALUES LESS THAN (MAXVALUE,MAXVALUE)
);

Each value used in a VALUES LESS THAN value list must match the type of the corresponding column exactly; no conversion is made. VALUES LESS THAN值列表中使用的每个值必须与相应列的类型完全匹配；未进行任何转换。For example, you cannot use the string '1' for a value that matches a column that uses an integer type (you must use the numeral 1 instead), nor can you use the numeral 1 for a value that matches a column that uses a string type (in such a case, you must use a quoted string: '1').例如，不能将字符串'1'用于与使用整数类型的列匹配的值（必须改用数字1），也不能将数字1用于与使用字符串类型的列匹配的值（在这种情况下，必须使用带引号的字符串：'1'）。

For more information, see Section 24.2.1, “RANGE Partitioning”, and Section 24.4, “Partition Pruning”.有关更多信息，请参阅第24.2.1节，“范围分区”和第24.4节，“分区修剪”。

LIST(expr)

This is useful when assigning partitions based on a table column with a restricted set of possible values, such as a state or country code. 这在基于表列分配分区时非常有用，表列具有一组受限的可能值，例如州或国家代码。In such a case, all rows pertaining to a certain state or country can be assigned to a single partition, or a partition can be reserved for a certain set of states or countries. 在这种情况下，可以将与某个州或国家有关的所有行分配给单个分区，也可以为某组州或国家保留分区。It is similar to RANGE, except that only VALUES IN may be used to specify permissible values for each partition.它与RANGE类似，不同的是只有VALUES IN可用于指定每个分区的允许值。

VALUES IN is used with a list of values to be matched. VALUES IN与要匹配的值列表一起使用。For instance, you could create a partitioning scheme such as the following:例如，您可以创建如下分区方案：

CREATE TABLE client_firms (
    id   INT,
    name VARCHAR(35)
)
PARTITION BY LIST (id) (
    PARTITION r0 VALUES IN (1, 5, 9, 13, 17, 21),
    PARTITION r1 VALUES IN (2, 6, 10, 14, 18, 22),
    PARTITION r2 VALUES IN (3, 7, 11, 15, 19, 23),
    PARTITION r3 VALUES IN (4, 8, 12, 16, 20, 24)
);

When using list partitioning, you must define at least one partition using VALUES IN. 使用列表分区时，必须使用VALUES IN定义至少一个分区。You cannot use VALUES LESS THAN with PARTITION BY LIST.不能将VALUES LESS THAN与PARTITION BY LIST配合使用。

LIST COLUMNS(column_list)

This variant on LIST facilitates partition pruning for queries using comparison conditions on multiple columns (that is, having conditions such as WHERE a = 5 AND b = 5 or WHERE a = 1 AND b = 10 AND c = 5). LIST上的这个变量有助于使用多列上的比较条件（即，具有诸如WHERE a = 5 AND b = 5或WHERE a = 1 AND b = 10 AND c = 5之类的条件）对查询进行分区修剪。It enables you to specify values in multiple columns by using a list of columns in the COLUMNS clause and a set of column values in each PARTITION ... VALUES IN (value_list) partition definition clause.它使您能够使用COLUMNS子句中的列列表和每个PARTITION ... VALUES IN (value_list)分区定义子句中的列值集来指定多列中的值。

The rules governing regarding data types for the column list used in LIST COLUMNS(column_list) and the value list used in VALUES IN(value_list) are the same as those for the column list used in RANGE COLUMNS(column_list) and the value list used in VALUES LESS THAN(value_list), respectively, except that in the VALUES IN clause, MAXVALUE is not permitted, and you may use NULL.关于LIST COLUMNS(column_list)中使用的列列表和VALUES IN(value_list)中使用的值列表的数据类型的规则分别与RANGE COLUMNS(column_list)中使用的列列表和VALUES LESS THAN(value_list)中使用的值列表的规则相同，但子句除外，不允许使用MAXVALUE，您可以使用NULL。

There is one important difference between the list of values used for VALUES IN with PARTITION BY LIST COLUMNS as opposed to when it is used with PARTITION BY LIST. 用于PARTITION BY LIST COLUMNS中的值的值列表与用于PARTITION BY LIST时的值列表有一个重要区别。When used with PARTITION BY LIST COLUMNS, each element in the VALUES IN clause must be a set of column values; the number of values in each set must be the same as the number of columns used in the COLUMNS clause, and the data types of these values must match those of the columns (and occur in the same order). 当与PARTITION BY LIST COLUMNS一起使用时，VALUES IN子句中的每个元素都必须是一组列值；每个集合中的值数必须与COLUMNS子句中使用的列数相同，并且这些值的数据类型必须与列的数据类型匹配（并且以相同的顺序出现）。In the simplest case, the set consists of a single column. 在最简单的情况下，集合由单个列组成。The maximum number of columns that can be used in the column_list and in the elements making up the value_list is 16.column_list和组成value_list的元素中可使用的最大列数为16。

The table defined by the following CREATE TABLE statement provides an example of a table using LIST COLUMNS partitioning:以下CREATE TABLE语句定义的表提供了一个使用LIST COLUMNS分区的表示例：

CREATE TABLE lc (
    a INT NULL,
    b INT NULL
)
PARTITION BY LIST COLUMNS(a,b) (
    PARTITION p0 VALUES IN( (0,0), (NULL,NULL) ),
    PARTITION p1 VALUES IN( (0,1), (0,2), (0,3), (1,1), (1,2) ),
    PARTITION p2 VALUES IN( (1,0), (2,0), (2,1), (3,0), (3,1) ),
    PARTITION p3 VALUES IN( (1,3), (2,2), (2,3), (3,2), (3,3) )
);

PARTITIONS num

The number of partitions may optionally be specified with a PARTITIONS num clause, where num is the number of partitions. 分区数可以选择使用PARTITIONS num子句指定，其中num是分区数。If both this clause and any PARTITION clauses are used, num must be equal to the total number of any partitions that are declared using PARTITION clauses.如果同时使用此子句和任何PARTITION子句，num必须等于使用PARTITION子句声明的任何分区的总数。

SUBPARTITION BY

A partition may optionally be divided into a number of subpartitions. 分区可以选择性地划分为若干子分区。This can be indicated by using the optional SUBPARTITION BY clause. 这可以通过使用可选的SUBPARTITION BY子句来表示。Subpartitioning may be done by HASH or KEY. 子分区可以通过HASH或KEY来完成。Either of these may be LINEAR. 这两者都可以是LINEAR的。These work in the same way as previously described for the equivalent partitioning types. 它们的工作方式与前面描述的等效分区类型相同。(It is not possible to subpartition by LIST or RANGE.)（无法按LIST或按RANGE细分。）

The number of subpartitions can be indicated using the SUBPARTITIONS keyword followed by an integer value.子分区的数量可以使用SUBPARTITIONS关键字后跟一个整数值来表示。

Rigorous checking of the value used in PARTITIONS or SUBPARTITIONS clauses is applied and this value must adhere to the following rules:对PARTITIONS或SUBPARTITIONS子句中使用的值进行严格检查，该值必须遵守以下规则：

partition_definition

Each partition may be individually defined using a partition_definition clause. 可以使用partition_definition子句单独定义每个分区。The individual parts making up this clause are as follows:构成本子句的各个部分如下：

subpartition_definition

The partition definition may optionally contain one or more subpartition_definition clauses. 分区定义可以选择性地包含一个或多个subpartition_definition子句。Each of these consists at a minimum of the SUBPARTITION name, where name is an identifier for the subpartition. 每个子分区至少包含SUBPARTITION name，其中name是子分区的标识符。Except for the replacement of the PARTITION keyword with SUBPARTITION, the syntax for a subpartition definition is identical to that for a partition definition.除了用SUBPARTITION替换PARTITION关键字外，SUBPARTITION定义的语法与PARTITION定义的语法相同。

Subpartitioning must be done by HASH or KEY, and can be done only on RANGE or LIST partitions. 子分区必须通过HASH或KEY完成，并且只能在RANGE分区或LIST分区上完成。See Section 24.2.6, “Subpartitioning”.请参阅第24.2.6节，“子分区”。