Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.omni.co/llms.txt

Use this file to discover all available pages before exploring further.

This parameter is primarily used when working with connections that have multiple databases configured. For most use cases, you won’t need to set this manually.
Specifies which database a table belongs to when a connection includes multiple databases. This is particularly useful for:
  • Multi-database PostgreSQL connections where tables from different databases need to be modeled in a single connection
  • Other database types that support catalog-level organization (BigQuery, Snowflake, MotherDuck, Databricks, Trino, Athena)
When you configure a connection with additional databases using Include Other Databases, Omni automatically sets the catalog for views from non-default databases. Queries are then automatically routed to the correct database at query time.

​
Limitations

Cross-database JOINs are not supported for PostgreSQL. Each query can only access tables from a single database.

​
Syntax

catalog: <catalog_name>

​
Properties

​
catalog
string
The name of the database catalog containing the table. This is typically set automatically when using the Include Other Databases connection setting.

​
Examples

Table from a secondary PostgreSQL database
catalog: secondary_db
schema: public
table_name: categories
Table from the default database (catalog not needed)
schema: public
table_name: orders