Movatterモバイル変換

MySQL 9.0 Reference Manual

15.2.7.1 INSERT ... SELECT Statement

INSERT [LOW_PRIORITY | HIGH_PRIORITY] [IGNORE]    [INTO]tbl_name    [PARTITION (partition_name [,partition_name] ...)]    [(col_name [,col_name] ...)]    {   SELECT ...       | TABLEtable_name       | VALUESrow_constructor_list    }    [ON DUPLICATE KEY UPDATEassignment_list]value:    {expr | DEFAULT}value_list:value [,value] ...row_constructor_list:    ROW(value_list)[, ROW(value_list)][, ...]assignment:col_name =value        | [row_alias.]col_name        | [tbl_name.]col_name        | [row_alias.]col_aliasassignment_list:assignment [,assignment] ...

WithINSERT ... SELECT, you can quickly insert many rows into a table from the result of aSELECT statement, which can select from one or many tables. For example:

INSERT INTO tbl_temp2 (fld_id)  SELECT tbl_temp1.fld_order_id  FROM tbl_temp1 WHERE tbl_temp1.fld_order_id > 100;

TABLE statement in place ofSELECT, as shown here:

INSERT INTO ta TABLE tb;

TABLE tb is equivalent toSELECT * FROM tb. It can be useful when inserting all columns from the source table into the target table, and no filtering with WHERE is required. In addition, the rows fromTABLE can be ordered by one or more columns usingORDER BY, and the number of rows inserted can be limited using aLIMIT clause. For more information, seeSection 15.2.16, “TABLE Statement”.

The following conditions hold forINSERT ... SELECT statements, and, except where noted, forINSERT ... TABLE as well:

SpecifyIGNORE to ignore rows that would cause duplicate-key violations.
The target table of theINSERT statement may appear in theFROM clause of theSELECT part of the query, or as the table named byTABLE. However, you cannot insert into a table and select from the same table in a subquery.
When selecting from and inserting into the same table, MySQL creates an internal temporary table to hold the rows from theSELECT and then inserts those rows into the target table. However, you cannot useINSERT INTO t ... SELECT ... FROM t whent is aTEMPORARY table, becauseTEMPORARY tables cannot be referred to twice in the same statement. For the same reason, you cannot useINSERT INTO t ... TABLE t whent is a temporary table. SeeSection 10.4.4, “Internal Temporary Table Use in MySQL”, andSection B.3.6.2, “TEMPORARY Table Problems”.
AUTO_INCREMENT columns work as usual.
To ensure that the binary log can be used to re-create the original tables, MySQL does not permit concurrent inserts forINSERT ... SELECT orINSERT ... TABLE statements (seeSection 10.11.3, “Concurrent Inserts”).
To avoid ambiguous column reference problems when theSELECT and theINSERT refer to the same table, provide a unique alias for each table used in theSELECT part, and qualify column names in that part with the appropriate alias.
TheTABLE statement does not support aliases.

You can explicitly select which partitions or subpartitions (or both) of the source or target table (or both) are to be used with aPARTITION clause following the name of the table. WhenPARTITION is used with the name of the source table in theSELECT portion of the statement, rows are selected only from the partitions or subpartitions named in its partition list. WhenPARTITION is used with the name of the target table for theINSERT portion of the statement, it must be possible to insert all rows selected into the partitions or subpartitions named in the partition list following the option. Otherwise, theINSERT ... SELECT statement fails. For more information and examples, seeSection 26.5, “Partition Selection”.

TABLE does not support aPARTITION clause.

ForINSERT ... SELECT statements, seeSection 15.2.7.2, “INSERT ... ON DUPLICATE KEY UPDATE Statement” for conditions under which theSELECT columns can be referred to in anON DUPLICATE KEY UPDATE clause. This also works forINSERT ... TABLE.

The order in which aSELECT orTABLE statement with noORDER BY clause returns rows is nondeterministic. This means that, when using replication, there is no guarantee that such aSELECT returns rows in the same order on the source and the replica, which can lead to inconsistencies between them. To prevent this from occurring, always writeINSERT ... SELECT orINSERT ... TABLE statements that are to be replicated using anORDER BY clause that produces the same row order on the source and the replica. See alsoSection 19.5.1.19, “Replication and LIMIT”.

Due to this issue,INSERT ... SELECT ON DUPLICATE KEY UPDATE andINSERT IGNORE ... SELECT statements are flagged as unsafe for statement-based replication. Such statements produce a warning in the error log when using statement-based mode and are written to the binary log using the row-based format when usingMIXED mode. (Bug #11758262, Bug #50439)

PREV HOME UP NEXT