RETURNING returns a resultset of the inserted rows.
#MYSQL SYNTAX INSERT VALUE UPDATE#
See INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE for further examples. SELECTing from another table: INSERT INTO contractor SELECT * FROM person WHERE status = 'c' Using the SET clause: INSERT INTO person SET first_name = 'John', last_name = 'Doe' Inserting more than 1 row at a time: INSERT INTO tbl_name VALUES ( 1, "row 1" ), ( 2, "row 2" ) Specifying the column names: INSERT INTO person ( first_name, last_name ) VALUES ( 'John', 'Doe' ) See INSERT - Default & Duplicate Values for details. INSERT DELAYEDįor more details on the DELAYED option, see INSERT DELAYED. See HIGH_PRIORITY and LOW_PRIORITY clauses for details. However, if one of these keywords is specified, concurrent inserts cannot be used.
This affects only storage engines that use only table-level locking (MyISAM, MEMORY, MERGE). If you use the HIGH_PRIORITY keyword, the statement has the same priority as SELECTs. If you use the LOW_PRIORITY keyword, execution of the INSERT is delayed until no other clients are reading from the table. However, the subquery cannot access the same table that is named in the INTO clause. Values can also be specified in the form of a SQL expression or subquery. All values are specified in the form col = expr. If many rows are inserted, this is a speed optimization.įor one-row statements, the SET clause may be more simple, because you don't need to remember the columns order. It is possible to specify more than one list to insert more than one rows with a single statement. The values must be listed in the same order as the columns list. The list of value follow the VALUES or VALUE keyword (which are interchangeable, regardless how much values you want to insert), and is wrapped by parenthesis. If this clause is not specified, all values must be explicitly specified, in the same order they are listed in the table definition. It specifies which values are explicitly inserted, and in which order. The RETURNING clause was introduced in MariaDB 10.5.
0 kommentar(er)
