All Products
Search
Document Center

Schema Exploration

Last Updated: Aug 11, 2020

InfluxQL is an SQL-like query language and you can use InfluxQL to interact with the data that is stored in TSDB for InfluxDB®. This topic describes the statements that you can use to query your schema.

SHOW DATABASES SHOW RETENTION POLICIES SHOW SERIES
SHOW MEASUREMENTS SHOW TAG KEYS SHOW TAG VALUES
SHOW FIELD KEYS - -

Sample data

You can download the sample data that is used in this topic from Sample data.

Before you use InfluxQL, log on to the influx command line interface (CLI).

  1. $ influx -precision rfc3339
  2. Connected to http://localhost:8086 version 1.7.x
  3. InfluxDB shell 1.7.x
  4. >

SHOW DATABASES

Returns the databases on which the current account has read permissions.
Notes: We recommend that you use the Time Series Database (TSDB) console to view and manage databases.

Syntax

  1. SHOW DATABASES

Example

Example 1: Execute a SHOW DATABASES statement

  1. > SHOW DATABASES
  2. name: databases
  3. name
  4. ----
  5. NOAA_water_database
  6. _internal

The statement returns the database names. The database names are organized in the tabular format. The current account has read permissions on two databases: NOAA_water_database and _internal.

SHOW RETENTION POLICIES

Returns all the retention policies for the specified database.
Notes: We recommend that you use the TSDB console to view and manage retention policies.

Syntax

  1. SHOW RETENTION POLICIES [ON <database_name>]

Syntax description

The ON <database_name> clause in the SHOW RETENTION POLICIES statement is optional. If the ON <database_name> clause is not included, you must execute the USE <database_name> statement in the CLI or use the db parameter in the HTTP API request to specify a database.

Examples

Example 1: Execute a SHOW RETENTION POLICIES statement that includes the ON clause

  1. > SHOW RETENTION POLICIES ON NOAA_water_database
  2. name duration shardGroupDuration replicaN default
  3. ---- -------- ------------------ -------- -------
  4. autogen 0s 168h0m0s 1 true

The statement returns all the retention policies for the NOAA_water_database database. The retention policies are organized in the tabular format. The autogen retention policy is returned in the query result. The autogen retention policy is the default retention policy for the database. If you use this retention policy, TSDB for InfluxDB® retains your data permanently, the time range covered by each shard group is seven days, and the replication factor is one.

Example 2: Execute a SHOW RETENTION POLICIES statement that does not include the ON clause

Execute the USE<database_name> statement to specify a database.

  1. > USE NOAA_water_database
  2. Using database NOAA_water_database
  3. > SHOW RETENTION POLICIES
  4. name duration shardGroupDuration replicaN default
  5. ---- -------- ------------------ -------- -------
  6. autogen 0s 168h0m0s 1 true

Use the db parameter in the HTTP API request to specify a database.

  1. ~# curl -G "http://localhost:8086/query?db=NOAA_water_database&pretty=true" --data-urlencode "q=SHOW RETENTION POLICIES"
  2. {
  3. "results": [
  4. {
  5. "statement_id": 0,
  6. "series": [
  7. {
  8. "columns": [
  9. "name",
  10. "duration",
  11. "shardGroupDuration",
  12. "replicaN",
  13. "default"
  14. ],
  15. "values": [
  16. [
  17. "autogen",
  18. "0s",
  19. "168h0m0s",
  20. 1,
  21. true
  22. ]
  23. ]
  24. }
  25. ]
  26. }
  27. ]
  28. }

SHOW SERIES

Returns the series for the specified database.

Syntax

  1. SHOW SERIES [ON <database_name>] [FROM_clause] [WHERE <tag_key> <operator> [ '<tag_value>' | <regular_expression>]] [LIMIT_clause] [OFFSET_clause]

Syntax description

The ON <database_name> clause in the SHOW SERIES statement is optional. If the ON <database_name> clause is not included, you must execute the USE <database_name> statement in the CLI or use the db parameter in the HTTP API request to specify a database.

The following clauses in the SHOW SERIES statement are optional: FROM, WHERE, LIMIT, and OFFSET clauses. You can use the WHERE clause in the SHOW SERIES statement to compare tags. In SHOW SERIES queries, field comparisons are invalid.

The WHERE clause supports the following operators:

= Equal to
<> Not equal to
! = Not equal to
=~ Match
! ~ Not match

For more information about regular expressions and FROM, LIMIT, and OFFSET clauses, see the Data exploration topic.

Examples

Example 1: Execute a SHOW SERIES statement that includes the ON clause

  1. > SHOW SERIES ON NOAA_water_database
  2. key
  3. ---
  4. average_temperature,location=coyote_creek
  5. average_temperature,location=santa_monica
  6. h2o_feet,location=coyote_creek
  7. h2o_feet,location=santa_monica
  8. h2o_pH,location=coyote_creek
  9. h2o_pH,location=santa_monica
  10. h2o_quality,location=coyote_creek,randtag=1
  11. h2o_quality,location=coyote_creek,randtag=2
  12. h2o_quality,location=coyote_creek,randtag=3
  13. h2o_quality,location=santa_monica,randtag=1
  14. h2o_quality,location=santa_monica,randtag=2
  15. h2o_quality,location=santa_monica,randtag=3
  16. h2o_temperature,location=coyote_creek
  17. h2o_temperature,location=santa_monica

The format of the query result is similar to the line protocol format. The portion that is located before the first comma (,) indicates the measurement name. The portion that follows the first comma (,) indicates tag keys or tag values. The NOAA_water_database stores 14 unique series for 5 different measurements.

Example 2: Execute a SHOW SERIES statement that does not include the ON clause

Execute the USE <database_name> statement to specify a database.

  1. > USE NOAA_water_database
  2. Using database NOAA_water_database
  3. > SHOW SERIES
  4. key
  5. ---
  6. average_temperature,location=coyote_creek
  7. average_temperature,location=santa_monica
  8. h2o_feet,location=coyote_creek
  9. h2o_feet,location=santa_monica
  10. h2o_pH,location=coyote_creek
  11. h2o_pH,location=santa_monica
  12. h2o_quality,location=coyote_creek,randtag=1
  13. h2o_quality,location=coyote_creek,randtag=2
  14. h2o_quality,location=coyote_creek,randtag=3
  15. h2o_quality,location=santa_monica,randtag=1
  16. h2o_quality,location=santa_monica,randtag=2
  17. h2o_quality,location=santa_monica,randtag=3
  18. h2o_temperature,location=coyote_creek
  19. h2o_temperature,location=santa_monica

Use the db parameter in the HTTP API request to specify a database.

  1. ~# curl -G "http://localhost:8086/query?db=NOAA_water_database&pretty=true" --data-urlencode "q=SHOW SERIES"
  2. {
  3. "results": [
  4. {
  5. "statement_id": 0,
  6. "series": [
  7. {
  8. "columns": [
  9. "key"
  10. ],
  11. "values": [
  12. [
  13. "average_temperature,location=coyote_creek"
  14. ],
  15. [
  16. "average_temperature,location=santa_monica"
  17. ],
  18. [
  19. "h2o_feet,location=coyote_creek"
  20. ],
  21. [
  22. "h2o_feet,location=santa_monica"
  23. ],
  24. [
  25. "h2o_pH,location=coyote_creek"
  26. ],
  27. [
  28. "h2o_pH,location=santa_monica"
  29. ],
  30. [
  31. "h2o_quality,location=coyote_creek,randtag=1"
  32. ],
  33. [
  34. "h2o_quality,location=coyote_creek,randtag=2"
  35. ],
  36. [
  37. "h2o_quality,location=coyote_creek,randtag=3"
  38. ],
  39. [
  40. "h2o_quality,location=santa_monica,randtag=1"
  41. ],
  42. [
  43. "h2o_quality,location=santa_monica,randtag=2"
  44. ],
  45. [
  46. "h2o_quality,location=santa_monica,randtag=3"
  47. ],
  48. [
  49. "h2o_temperature,location=coyote_creek"
  50. ],
  51. [
  52. "h2o_temperature,location=santa_monica"
  53. ]
  54. ]
  55. }
  56. ]
  57. }
  58. ]
  59. }

Example 3: Execute a SHOW SERIES statement that includes multiple clauses

  1. > SHOW SERIES ON NOAA_water_database FROM "h2o_quality" WHERE "location" = 'coyote_creek' LIMIT 2
  2. key
  3. ---
  4. h2o_quality,location=coyote_creek,randtag=1
  5. h2o_quality,location=coyote_creek,randtag=2

The statement returns all the series that are associated with the h2o_quality measurement in the NOAA_water_database database. The returned series contain the location = coyote_creek tag key-value pair. The LIMIT clause limits the number of returned series to two.

SHOW MEASUREMENTS

Returns the measurements for the specified database.

Syntax

  1. SHOW MEASUREMENTS [ON <database_name>] [WITH MEASUREMENT <regular_expression>] [WHERE <tag_key> <operator> ['<tag_value>' | <regular_expression>]] [LIMIT_clause] [OFFSET_clause]

Syntax description

The ON <database_name> clause in the SHOW MEASUREMENTS statement is optional. If the ON <database_name> clause is not included, you must execute the USE <database_name> statement in the CLI or use the db parameter in the HTTP API request to specify a database.

The following clauses in the SHOW MEASUREMENTS statement are optional: WITH, WHERE, LIMIT, and OFFSET clauses. You can use the WHERE clause in the SHOW MEASUREMENTS statement to compare tags. In SHOW MEASUREMENTS queries, field comparisons are invalid.

The WHERE clause supports the following operators:

= Equal to
<> Not equal to
! = Not equal to
=~ Match
! ~ Not match

For more information about regular expressions and LIMIT and OFFSET clauses, see the Data exploration topic.

Examples

Example 1: Execute a SHOW MEASUREMENTS statement that includes the ON clause

  1. > SHOW MEASUREMENTS ON NOAA_water_database
  2. name: measurements
  3. name
  4. ----
  5. average_temperature
  6. h2o_feet
  7. h2o_pH
  8. h2o_quality
  9. h2o_temperature

The statement returns the measurements that are stored in the NOAA_water_database database. The NOAA_water_database database stores five measurements: average_temperature, h2o_feet, h2o_pH, h2o_quality, and h2o_temperature.

Example 2: Execute a SHOW MEASUREMENTS statement that does not include the ON clause

Execute the USE <database_name> statement to specify a database.

  1. > USE NOAA_water_database
  2. Using database NOAA_water_database
  3. > SHOW MEASUREMENTS
  4. name: measurements
  5. name
  6. ----
  7. average_temperature
  8. h2o_feet
  9. h2o_pH
  10. h2o_quality
  11. h2o_temperature

Use the db parameter in the HTTP API request to specify a database.

  1. ~# curl -G "http://localhost:8086/query?db=NOAA_water_database&pretty=true" --data-urlencode "q=SHOW MEASUREMENTS"
  2. {
  3. {
  4. "results": [
  5. {
  6. "statement_id": 0,
  7. "series": [
  8. {
  9. "name": "measurements",
  10. "columns": [
  11. "name"
  12. ],
  13. "values": [
  14. [
  15. "average_temperature"
  16. ],
  17. [
  18. "h2o_feet"
  19. ],
  20. [
  21. "h2o_pH"
  22. ],
  23. [
  24. "h2o_quality"
  25. ],
  26. [
  27. "h2o_temperature"
  28. ]
  29. ]
  30. }
  31. ]
  32. }
  33. ]
  34. }

Example 3: Execute a SHOW MEASUREMENTS statement that includes multiple clauses (a)

  1. > SHOW MEASUREMENTS ON NOAA_water_database WITH MEASUREMENT =~ /h2o.*/ LIMIT 2 OFFSET 1
  2. name: measurements
  3. name
  4. ----
  5. h2o_pH
  6. h2o_quality

The statement returns the measurements whose names start with h2o in the NOAA_water_database database. The LIMIT clause limits the number of returned measurement names to two. The OFFSET clause is specified to skip the first measurement h2o_feet. Therefore, the statement returns the two measurements that follow the h2o_feet measurement.

Example 4: Execute a SHOW MEASUREMENTS statement that includes multiple clauses (b)

  1. > SHOW MEASUREMENTS ON NOAA_water_database WITH MEASUREMENT =~ /h2o.*/ WHERE "randtag" =~ /\d/
  2. name: measurements
  3. name
  4. ----
  5. h2o_quality

The statement returns the measurements that are stored in the NOAA_water_database database. The names of the measurements start with h2o and the randtag tag values in the measurements contain integers.

SHOW TAG KEYS

Returns the tag keys for the specified database.

Syntax

  1. SHOW TAG KEYS [ON <database_name>] [FROM_clause] [WHERE <tag_key> <operator> ['<tag_value>' | <regular_expression>]] [LIMIT_clause] [OFFSET_clause]

Syntax description

The ON <database_name> clause in the SHOW TAG KEYS statement is optional. If the ON <database_name> clause is not included, you must execute the USE <database_name> statement in the CLI or use the db parameter in the HTTP API request to specify a database.

The following clauses in the SHOW TAG KEYS statement are optional: FROM and WHERE clauses. You can use the WHERE clause in the SHOW TAG KEYS statement to compare tags. In SHOW TAG KEYS queries, field comparisons are invalid.

The WHERE clause supports the following operators:

= Equal to
<> Not equal to
! = Not equal to
=~ Match
! ~ Not match

For more information about regular expressions and FROM, LIMIT, and OFFSET clauses, see the Data exploration topic.

Examples

Example 1: Execute a SHOW TAG KEYS statement that includes the ON clause

  1. > SHOW TAG KEYS ON "NOAA_water_database"
  2. name: average_temperature
  3. tagKey
  4. ------
  5. location
  6. name: h2o_feet
  7. tagKey
  8. ------
  9. location
  10. name: h2o_pH
  11. tagKey
  12. ------
  13. location
  14. name: h2o_quality
  15. tagKey
  16. ------
  17. location
  18. randtag
  19. name: h2o_temperature
  20. tagKey
  21. ------
  22. location

The statement returns the tag keys that are stored in the NOAA_water_database database. The query results are grouped by measurement name. The query results show that each measurement has a tag key named location. The h2o_quality measurement has two tag keys: location and randtag.

Example 2: Execute a SHOW TAG KEYS statement that does not include the ON clause

Execute the USE <database_name> statement to specify a database.

  1. > USE NOAA_water_database
  2. Using database NOAA_water_database
  3. > SHOW TAG KEYS
  4. name: average_temperature
  5. tagKey
  6. ------
  7. location
  8. name: h2o_feet
  9. tagKey
  10. ------
  11. location
  12. name: h2o_pH
  13. tagKey
  14. ------
  15. location
  16. name: h2o_quality
  17. tagKey
  18. ------
  19. location
  20. randtag
  21. name: h2o_temperature
  22. tagKey
  23. ------
  24. location

Use the db parameter in the HTTP API request to specify a database.

  1. ~# curl -G "http://localhost:8086/query?db=NOAA_water_database&pretty=true" --data-urlencode "q=SHOW TAG KEYS"
  2. {
  3. "results": [
  4. {
  5. "statement_id": 0,
  6. "series": [
  7. {
  8. "name": "average_temperature",
  9. "columns": [
  10. "tagKey"
  11. ],
  12. "values": [
  13. [
  14. "location"
  15. ]
  16. ]
  17. },
  18. {
  19. "name": "h2o_feet",
  20. "columns": [
  21. "tagKey"
  22. ],
  23. "values": [
  24. [
  25. "location"
  26. ]
  27. ]
  28. },
  29. {
  30. "name": "h2o_pH",
  31. "columns": [
  32. "tagKey"
  33. ],
  34. "values": [
  35. [
  36. "location"
  37. ]
  38. ]
  39. },
  40. {
  41. "name": "h2o_quality",
  42. "columns": [
  43. "tagKey"
  44. ],
  45. "values": [
  46. [
  47. "location"
  48. ],
  49. [
  50. "randtag"
  51. ]
  52. ]
  53. },
  54. {
  55. "name": "h2o_temperature",
  56. "columns": [
  57. "tagKey"
  58. ],
  59. "values": [
  60. [
  61. "location"
  62. ]
  63. ]
  64. }
  65. ]
  66. }
  67. ]
  68. }

Example 3: Execute a SHOW TAG KEYS statement that includes multiple clauses

  1. > SHOW TAG KEYS ON "NOAA_water_database" FROM "h2o_quality" LIMIT 1 OFFSET 1
  2. name: h2o_quality
  3. tagKey
  4. ------
  5. randtag

The statement returns the tag keys that are associated with the h2o_quality measurement in NOAA_water_database database. The LIMIT clause limits the number of returned tag keys to one. The OFFSET clause is specified to skip the first tag key. Therefore, the statement returns the tag key that follows the first tag key.

SHOW TAG VALUES

Returns the tag values of the specified tag keys in the database.

Syntax

  1. SHOW TAG VALUES [ON <database_name>][FROM_clause] WITH KEY [ [<operator> "<tag_key>" | <regular_expression>] | [IN ("<tag_key1>","<tag_key2")]] [WHERE <tag_key> <operator> ['<tag_value>' | <regular_expression>]] [LIMIT_clause] [OFFSET_clause]

Syntax description

The ON <database_name> clause in the SHOW TAG VALUES statement is optional. If the ON <database_name> clause is not included, you must execute the USE <database_name> statement in the CLI or use the db parameter in the HTTP API request to specify a database.

You must specify the WITH clause in the SHOW TAG VALUES statement. In the WITH clause, you can specify one or more tag keys, or a regular expression.

The following clauses are optional: FROM, WHERE, LIMIT, and OFFSET clauses. You can use the WHERE clause to compare tags. In SHOW TAG VALUES queries, field comparisons are invalid.

WITH and WHERE clauses support the following operators:

= Equal to
<> Not equal to
! = Not equal to
=~ Match
! ~ Not match

For more information about regular expressions and FROM, LIMIT, and OFFSET clauses, see the Data exploration topic.

Examples

Example 1: Execute a SHOW TAG VALUES statement that includes the ON clause

  1. > SHOW TAG VALUES ON "NOAA_water_database" WITH KEY = "randtag"
  2. name: h2o_quality
  3. key value
  4. --- -----
  5. randtag 1
  6. randtag 2
  7. randtag 3

The statement returns the tag values of the randtag tag key in the NOAA_water_database database. The query results of the SHOW TAG VALUES statement are grouped by measurement name.

Example 2: Execute a SHOW TAG VALUES statement that does not include the ON clause

Execute the USE <database_name> statement to specify a database.

  1. > USE NOAA_water_database
  2. Using database NOAA_water_database
  3. > SHOW TAG VALUES WITH KEY = "randtag"
  4. name: h2o_quality
  5. key value
  6. --- -----
  7. randtag 1
  8. randtag 2
  9. randtag 3

Use the db parameter in the HTTP API request to specify a database.

  1. ~# curl -G "http://localhost:8086/query?db=NOAA_water_database&pretty=true" --data-urlencode 'q=SHOW TAG VALUES WITH KEY = "randtag"'
  2. {
  3. "results": [
  4. {
  5. "statement_id": 0,
  6. "series": [
  7. {
  8. "name": "h2o_quality",
  9. "columns": [
  10. "key",
  11. "value"
  12. ],
  13. "values": [
  14. [
  15. "randtag",
  16. "1"
  17. ],
  18. [
  19. "randtag",
  20. "2"
  21. ],
  22. [
  23. "randtag",
  24. "3"
  25. ]
  26. ]
  27. }
  28. ]
  29. }
  30. ]
  31. }

Example 3: Execute a SHOW TAG VALUES statement that includes multiple clauses

  1. > SHOW TAG VALUES ON "NOAA_water_database" WITH KEY IN ("location","randtag") WHERE "randtag" =~ /./ LIMIT 3
  2. name: h2o_quality
  3. key value
  4. --- -----
  5. location coyote_creek
  6. location santa_monica
  7. randtag 1

The statement returns the tag values of the location and randtag tag keys for all the measurements in the NOAA_water_database database. The returned tag values of the randtag tag key do not include NULL values. The LIMIT clause limits the number of returned tag values to three.

SHOW FIELD KEYS

Returns the field keys and the data types of the field values.

Syntax

  1. SHOW FIELD KEYS [ON <database_name>] [FROM <measurement_name>]

Syntax description

The ON <database_name> clause in the SHOW FIELD KEYS statement is optional. If the ON <database_name> clause is not included, you must execute the USE <database_name> statement in the CLI or use the db parameter in the HTTP API request to specify a database.

The FROM clause in the SHOW FIELD KEYS statement is also optional. For more information about the FROM clause, see the “Data exploration” topic.

Notes: The data types of your field values can be different across shards. If the field values of various data types exist, the SHOW FIELD KEYS statement returns the field keys based on data types in descending order: FLOAT, INT, STRING, and BOOLEAN.

Examples

Example 1: Execute a SHOW FIELD KEYS statement that includes the ON clause

  1. > SHOW FIELD KEYS ON "NOAA_water_database"
  2. name: average_temperature
  3. fieldKey fieldType
  4. -------- ---------
  5. degrees float
  6. name: h2o_feet
  7. fieldKey fieldType
  8. -------- ---------
  9. level description string
  10. water_level float
  11. name: h2o_pH
  12. fieldKey fieldType
  13. -------- ---------
  14. pH float
  15. name: h2o_quality
  16. fieldKey fieldType
  17. -------- ---------
  18. index float
  19. name: h2o_temperature
  20. fieldKey fieldType
  21. -------- ---------
  22. degrees float

The statement returns the field keys and the data types of the field value for each measurement in the NOAA_water_database database.

Example 2: Execute a SHOW FIELD KEYS statement that does not include the ON clause

Execute the USE <database_name> statement to specify a database.

  1. > USE NOAA_water_database
  2. Using database NOAA_water_database
  3. > SHOW FIELD KEYS
  4. name: average_temperature
  5. fieldKey fieldType
  6. -------- ---------
  7. degrees float
  8. name: h2o_feet
  9. fieldKey fieldType
  10. -------- ---------
  11. level description string
  12. water_level float
  13. name: h2o_pH
  14. fieldKey fieldType
  15. -------- ---------
  16. pH float
  17. name: h2o_quality
  18. fieldKey fieldType
  19. -------- ---------
  20. index float
  21. name: h2o_temperature
  22. fieldKey fieldType
  23. -------- ---------
  24. degrees float

Use the db parameter in the HTTP API request to specify a database.

  1. ~# curl -G "http://localhost:8086/query?db=NOAA_water_database&pretty=true" --data-urlencode 'q=SHOW FIELD KEYS'
  2. {
  3. "results": [
  4. {
  5. "statement_id": 0,
  6. "series": [
  7. {
  8. "name": "average_temperature",
  9. "columns": [
  10. "fieldKey",
  11. "fieldType"
  12. ],
  13. "values": [
  14. [
  15. "degrees",
  16. "float"
  17. ]
  18. ]
  19. },
  20. {
  21. "name": "h2o_feet",
  22. "columns": [
  23. "fieldKey",
  24. "fieldType"
  25. ],
  26. "values": [
  27. [
  28. "level description",
  29. "string"
  30. ],
  31. [
  32. "water_level",
  33. "float"
  34. ]
  35. ]
  36. },
  37. {
  38. "name": "h2o_pH",
  39. "columns": [
  40. "fieldKey",
  41. "fieldType"
  42. ],
  43. "values": [
  44. [
  45. "pH",
  46. "float"
  47. ]
  48. ]
  49. },
  50. {
  51. "name": "h2o_quality",
  52. "columns": [
  53. "fieldKey",
  54. "fieldType"
  55. ],
  56. "values": [
  57. [
  58. "index",
  59. "float"
  60. ]
  61. ]
  62. },
  63. {
  64. "name": "h2o_temperature",
  65. "columns": [
  66. "fieldKey",
  67. "fieldType"
  68. ],
  69. "values": [
  70. [
  71. "degrees",
  72. "float"
  73. ]
  74. ]
  75. }
  76. ]
  77. }
  78. ]
  79. }

Example 3: Execute a SHOW FIELD KEYS statement that includes the FROM clause

  1. > SHOW FIELD KEYS ON "NOAA_water_database" FROM "h2o_feet"
  2. name: h2o_feet
  3. fieldKey fieldType
  4. -------- ---------
  5. level description string
  6. water_level float

The statement returns the fields keys and the data types of the field values for the h2o_feet measurement in the NOAA_water_database database.

SHOW FIELD KEYS FAQ

What are the impacts on the SHOW FIELD KEYS statement if my database stores the field values of various data types?

The data types of the field values must be the same in the same shard, but can be different across shards. The SHOW FIELD KEYS statement scans each shard and returns the data types that are associated with the specified field key.

Example

The all_the_types field stores the data of four data types.

  1. > SHOW FIELD KEYS
  2. name: mymeas
  3. fieldKey fieldType
  4. -------- ---------
  5. all_the_types integer
  6. all_the_types float
  7. all_the_types string
  8. all_the_types boolean

Notes: The SHOW FIELD KEYS statement handles the data type differences of field values in a different way from the SELECT statement. For more information, see the FAQ topic.


InfluxDB® is a trademark registered by InfluxData, which is not affiliated with, and does not endorse, TSDB for InfluxDB®.