Documentation

Quotation

Limited availability

InfluxDB Clustered is currently 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.

InfluxQL supports both single and double quotation marks, but they each function differently and serve different purposes.

Single quotes

Use single quotation marks (') in the string literal and timestamp literal syntax.

In the following example, the WHERE clause evaluates the value of the room tag. Tags only contain string values, so the right operand of the predicate expression should be a string literal.

... WHERE room = 'Kitchen'

Double quotes

Use double quotation marks (") to quote identifiers. Identifiers must be double-quoted in the following cases:

  • The identifier contains non-word characters. Word characters are defined as [a-z,A-Z,0-9,_].
  • The identifier is case-sensitive.
  • The identifier contains InfluxQL keywords.
  • The identifier begins with a digit.

Double-quoted identifiers can also:

  • Contain any Unicode character except for a new line.
  • Contain escaped " characters (for example: \").
  • Include InfluxQL keywords.

While not always necessary, we recommend that you double quote identifiers.

InfluxQL quoting guidelines differ from line protocol quoting guidelines.


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: