![]() |
![]()
| ![]() |
![]()
NAMEVALUES - compute a set of rowsSYNOPSISVALUES ( expression [, ...] ) [, ...] [ ORDER BY sort_expression [ ASC | DESC | USING operator ] [, ...] ] [ LIMIT { count | ALL } ] [ OFFSET start [ ROW | ROWS ] ] [ FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY ] DESCRIPTIONVALUES computes a row value or set of row values specified by value expressions. It is most commonly used to generate a “constant table” within a larger command, but it can be used on its own. When more than one row is specified, all the rows must have the same number of elements. The data types of the resulting table's columns are determined by combining the explicit or inferred types of the expressions appearing in that column, using the same rules as for UNION (see Section 10.5, “UNION, CASE, and Related Constructs”, in the documentation). Within larger commands, VALUES is syntactically allowed anywhere that SELECT is. Because it is treated like a SELECT by the grammar, it is possible to use the ORDER BY, LIMIT (or equivalently FETCH FIRST), and OFFSET clauses with a VALUES command.PARAMETERSexpressionA constant or expression to compute and insert at the
indicated place in the resulting table (set of rows). In a VALUES list
appearing at the top level of an INSERT, an expression can be
replaced by DEFAULT to indicate that the destination column's default value
should be inserted. DEFAULT cannot be used when VALUES appears in other
contexts.
sort_expression
An expression or integer constant indicating how to sort
the result rows. This expression can refer to the columns of the VALUES
result as column1, column2, etc. For more details see ORDER BY Clause.
operator
A sorting operator. For details see ORDER BY
Clause.
count
The maximum number of rows to return. For details see
LIMIT Clause.
start
The number of rows to skip before starting to return
rows. For details see LIMIT Clause.
NOTESVALUES lists with very large numbers of rows should be avoided, as you might encounter out-of-memory failures or poor performance. VALUES appearing within INSERT is a special case (because the desired column types are known from the INSERT's target table, and need not be inferred by scanning the VALUES list), so it can handle larger lists than are practical in other contexts.EXAMPLESA bare VALUES command:VALUES (1, 'one'), (2, 'two'), (3, 'three'); SELECT 1 AS column1, 'one' AS column2 UNION ALL SELECT 2, 'two' UNION ALL SELECT 3, 'three'; INSERT INTO films (code, title, did, date_prod, kind) VALUES ('T_601', 'Yojimbo', 106, '1961-06-16', 'Drama'); INSERT INTO films VALUES ('UA502', 'Bananas', 105, DEFAULT, 'Comedy', '82 minutes'), ('T_601', 'Yojimbo', 106, DEFAULT, 'Drama', DEFAULT); SELECT f.* FROM films f, (VALUES('MGM', 'Horror'), ('UA', 'Sci-Fi')) AS t (studio, kind) WHERE f.studio = t.studio AND f.kind = t.kind; UPDATE employees SET salary = salary * v.increase FROM (VALUES(1, 200000, 1.2), (2, 400000, 1.4)) AS v (depno, target, increase) WHERE employees.depno = v.depno AND employees.sales >= v.target; SELECT * FROM machines WHERE ip_address IN (VALUES('192.168.0.1'::inet), ('192.168.0.10'), ('192.168.1.43')); COMPATIBILITYVALUES conforms to the SQL standard. LIMIT and OFFSET are PostgreSQL extensions; see also under SELECT(7).SEE ALSOINSERT(7), SELECT(7)
|