*** DRAFT ***
The INSERT statement comes in three basic forms.
INSERT INTO table VALUES(...);
R-21490-41092:[The first form (with the "VALUES" keyword) creates one or more new rows in an existing table. ] R-19218-01018:[If the column-name list after table-name is omitted then the number of values inserted into each row must be the same as the number of columns in the table. ] R-29730-42609:[In this case the result of evaluating the left-most expression from each term of the VALUES list is inserted into the left-most column of each new row, and so forth for each subsequent expression. ] R-21115-58321:[If a column-name list is specified, then the number of values in each term of the VALUE list must match the number of specified columns. ] R-07016-26442:[Each of the named columns of the new row is populated with the results of evaluating the corresponding VALUES expression. ] R-12183-43719:[Table columns that do not appear in the column list are populated with the default column value (specified as part of the CREATE TABLE statement), or with NULL if no default value is specified. ]
INSERT INTO table SELECT ...;
The second form of the INSERT statement contains a SELECT statement instead of a VALUES clause. R-52173-30215:[A new entry is inserted into the table for each row of data returned by executing the SELECT statement. ] R-63614-47421:[If a column-list is specified, the number of columns in the result of the SELECT must be the same as the number of items in the column-list. ] R-58951-07798:[Otherwise, if no column-list is specified, the number of columns in the result of the SELECT must be the same as the number of columns in the table. ] R-31074-37730:[Any SELECT statement, including compound SELECTs and SELECT statements with ORDER BY and/or LIMIT clauses, may be used in an INSERT statement of this form. ]
To avoid a parsing ambiguity, the SELECT statement should always contain a WHERE clause, even if that clause is simply "WHERE true", if the upsert-clause is present. Without the WHERE clause, the parser does not know if the token "ON" is part of a join constraint on the SELECT, or the beginning of the upsert-clause.
INSERT INTO table DEFAULT VALUES;
The third form of an INSERT statement is with DEFAULT VALUES. R-25149-22012:[The INSERT ... DEFAULT VALUES statement inserts a single new row into the named table. ] R-18927-01951:[Each column of the new row is populated with its default value, or with a NULL if no default value is specified as part of the column definition in the CREATE TABLE statement. ] The upsert-clause is not supported after DEFAULT VALUES.
R-00267-47727:[The initial "INSERT" keyword can be replaced by "REPLACE" or "INSERT OR action" to specify an alternative constraint conflict resolution algorithm to use during that one INSERT command. ] For compatibility with MySQL, R-23110-47146:[the parser allows the use of the single keyword REPLACE as an alias for "INSERT OR REPLACE". ]
R-59829-49719:[The optional "schema-name." prefix on the table-name is supported for top-level INSERT statements only. ] R-05731-00924:[The table name must be unqualified for INSERT statements that occur within CREATE TRIGGER statements. ] R-15888-36326:[Similarly, the "DEFAULT VALUES" form of the INSERT statement is supported for top-level INSERT statements only and not for INSERT statements within triggers. ]
The optional "AS alias" phrase provides an alternative name for the table into which content is being inserted. The alias name can be used within WHERE and SET clauses of the UPSERT. If there is no upsert-clause, then the alias is pointless, but also harmless.
See the separate UPSERT documentation for the additional trailing syntax that can cause an INSERT to behave as an UPDATE if the INSERT would otherwise violate a uniqueness constraint. The upsert clause is not allowed on an "INSERT ... DEFAULT VALUES".
This page last modified on 2022-01-08 05:02:57 UTC
*** DRAFT ***