Documentation

Table value constructor

The table value constructor (TVC) uses the VALUES keyword to specify a set of row value expressions to construct into a table. The TVC can be used in the FROM clause to build an ad hoc table at query time.

VALUES (row_value_list)[,...n]
Arguments
  • row_value_list: Comma-delimited list of column values. Enclose each list in parentheses and separate multiple lists with commas. Each list must have the same number of values and values must be in the same order as columns in the table. Each list must contain a value for each column.

Usage

SELECT
  expression[,...n]
FROM
  (VALUES (row_value_list)[,...n]) [AS] table_name(column_name[,...n])

When using the TVC, the AS keyword is optional and implied when naming the table and providing column names.

Examples

Select data from an ad hoc table

SELECT *
FROM
  (VALUES ('2023-01-01 12:00:00'::TIMESTAMP, 1.23, 4.56),
          ('2023-01-01 13:00:00'::TIMESTAMP, 2.46, 8.1),
          ('2023-01-01 13:00:00'::TIMESTAMP, 4.81, 16.2)
  ) AS data(time, f1, f2)
time f1 f2
2023-01-01T12:00:00Z 1.23 4.56
2023-01-01T13:00:00Z 2.46 8.1
2023-01-01T13:00:00Z 4.81 16.2

Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: