IMPORT TABLE FROM sdi_file [, sdi_file] ...

IMPORT TABLE 语句根据 .sdi（序列化字典信息）元数据文件中的信息导入 MyISAM 表。IMPORT TABLE 需要具有读取 .sdi 和表内容文件的 FILE 权限，以及创建表所需的 CREATE 权限。The IMPORT TABLE statement imports MyISAM tables based on information contained in .sdi (serialized dictionary information) metadata files. IMPORT TABLE requires the FILE privilege to read the .sdi and table content files, and the CREATE privilege for the table to be created.

表可以通过在一台服务器上使用 mysqldump 导出为 SQL 语句文件，并在另一台服务器上使用 mysql 处理该 dump 文件导入。IMPORT TABLE 提供了一种使用表文件的 “raw” 方式更快速的替代方法。Tables can be exported from one server using mysqldump to write a file of SQL statements and imported into another server using mysql to process the dump file. IMPORT TABLE provides a faster alternative using the “raw” table files.

在导入之前，提供表内容的文件必须放置在导入服务器的相应模式目录中，且 .sdi 文件必须位于服务器可访问的目录中。例如，.sdi 文件可以放置在由系统变量 secure_file_priv 指定的目录中，或者（如果 secure_file_priv 为空）放在服务器数据目录下的某个目录中。Prior to import, the files that provide the table content must be placed in the appropriate schema directory for the import server, and the .sdi file must be located in a directory accessible to the server. For example, the .sdi file can be placed in the directory named by the secure_file_priv system variable, or (if secure_file_priv is empty) in a directory under the server data directory.

下面的示例描述了如何将一个服务器的 hr 模式中名为 employees 和 managers 的 MyISAM 表导出，并导入到另一服务器的 hr 模式中。该示例使用了以下假设（要在您自己的系统上执行类似操作，请根据需要修改路径名）：The following example describes how to export MyISAM tables named employees and managers from the hr schema of one server and import them into the hr schema of another server. The example uses these assumptions (to perform a similar operation on your own system, modify the path names as appropriate):

要从导出服务器导出表，请使用以下步骤：To export tables from the export server, use this procedure:

要将表导入到导入服务器，请使用以下步骤：To import tables into the import server, use this procedure:

如果 secure_file_priv 系统变量为空，则 .sdi 文件不必放在导入服务器目录中；它可以放在服务器可以访问的任何目录，包括导入表的模式目录。然而，如果 .sdi 文件放在该目录中，它可能会被重写；导入操作会为表创建一个新的 .sdi 文件，如果操作为新文件使用相同的文件名，将会覆盖旧的 .sdi 文件。The .sdi file need not be placed in the import server directory named by the secure_file_priv system variable if that variable is empty; it can be in any directory accessible to the server, including the schema directory for the imported table. If the .sdi file is placed in that directory, however, it may be rewritten; the import operation creates a new .sdi file for the table, which overwrites the old .sdi file if the operation uses the same file name for the new file.

每个 sdi_file 值必须是一个字符串字面值，指定表的 .sdi 文件，或者是匹配 .sdi 文件的模式。如果字符串是一个模式，任何前导目录路径和 .sdi 文件名后缀必须逐字提供。模式字符仅允许出现在文件名的基本名部分：Each sdi_file value must be a string literal that names the .sdi file for a table or is a pattern that matches .sdi files. If the string is a pattern, any leading directory path and the .sdi file name suffix must be given literally. Pattern characters are permitted only in the base name part of the file name:

使用模式时，前面的 IMPORT TABLE 语句可以这样编写（假设 /tmp/mysql-files 目录中没有其他匹配该模式的 .sdi 文件）：Using a pattern, the previous IMPORT TABLE statement could have been written like this (assuming that the /tmp/mysql-files directory contains no other .sdi files matching the pattern):

IMPORT TABLE FROM '/tmp/mysql-files/*.sdi';

为了解释 .sdi 文件路径名的位置，服务器使用与 IMPORT TABLE 相同的规则，作为服务器端 LOAD DATA 的规则（即非 LOCAL 规则）。参见 第 15.2.9 章，“LOAD DATA 语句”，特别注意用于解释相对路径名的规则。To interpret the location of .sdi file path names, the server uses the same rules for IMPORT TABLE as the server-side rules for LOAD DATA (that is, the non-LOCAL rules). See Section 15.2.9, “LOAD DATA Statement”, paying particular attention to the rules used to interpret relative path names.

IMPORT TABLE 如果无法找到 .sdi 或表文件则会失败。导入表后，服务器会尝试打开它，并报告任何检测到的问题作为警告。要尝试修复以纠正任何报告的问题，请使用 REPAIR TABLE。IMPORT TABLE fails if the .sdi or table files cannot be located. After importing a table, the server attempts to open it and reports as warnings any problems detected. To attempt a repair to correct any reported issues, use REPAIR TABLE.

IMPORT TABLE 不会写入二进制日志。IMPORT TABLE is not written to the binary log.

{
   "mysqld_version_id":80019,
   "dd_version":80017,
   "sdi_version":80016,
   ...
}