INFORMATION_SCHEMA: its column names, order, and data types.
Supported views
information_schema.tables(BigQuery reference).information_schema.columns(BigQuery reference).information_schema.jobs/jobs_by_user/jobs_by_project(BigQuery reference). Region-qualified; see below.information_schema.views(BigQuery reference).information_schema.schemata(BigQuery reference).information_schema.routines(BigQuery reference).information_schema.object_privileges(BigQuery reference).information_schema.search_indexes(BigQuery reference).information_schema.vector_indexes(BigQuery reference).
INFORMATION_SCHEMA view not listed does not exist in BigQuery mode: querying it raises a “relation does not exist” error.
Addressing
A supported view is reachable by the BigQuery dataset-qualified forms as well as the bare form:INFORMATION_SCHEMA.TABLES: the current database, all datasets.<dataset>.INFORMATION_SCHEMA.TABLES: one dataset (table_schema = '<dataset>').<project>.<dataset>.INFORMATION_SCHEMA.TABLES:<project>selects the database,<dataset>the schema.
`region-us`.INFORMATION_SCHEMA.*) are rejected for dataset-scoped views. The JOBS family is region-scoped in BigQuery (`region-us`.INFORMATION_SCHEMA.JOBS); Firebolt has no regions, so the region qualifier is accepted and ignored, and the bare form works too.
Notes
- Type-valued columns carry Firebolt spellings, not BigQuery’s:
tables.ddlreturns Firebolt DDL,columns.data_typereturns Firebolt type names (BIGINT,TEXT),views.view_definitionreturns Firebolt DDL, andtables.table_typemay carry Firebolt-specific values (for exampleEXTERNAL) for objects with no BigQuery equivalent. pg_cataloghas no BigQuery equivalent and is not available in BigQuery mode; referencing it raises a “relation does not exist” error.