SHOW SEMANTIC FACTS

Lists facts (named row-level expressions) registered in one or all semantic views. Each row describes a single fact with its name, source table, inferred data type, synonyms, and comment. Views that have no facts defined return no rows.

Syntax

SHOW SEMANTIC FACTS
    [ LIKE '<pattern>' ]
    [ IN <name> ]
    [ IN SCHEMA <schema_name> | IN DATABASE <database_name> ]
    [ STARTS WITH '<prefix>' ]
    [ LIMIT <rows> ]

All clauses are optional. When multiple clauses appear, they must follow the order shown above.

Statement Variants

SHOW SEMANTIC FACTS

Returns facts across all registered semantic views, sorted by semantic view name and then fact name. Views with no FACTS clause are omitted from the result.

SHOW SEMANTIC FACTS IN <name>

Returns facts for the specified semantic view only, sorted by fact name. Returns an error if the view does not exist. Returns an empty result if the view has no facts.

Parameters

<name>

The name of the semantic view. Required only for the single-view form (IN clause). Returns an error if the view does not exist.

Optional Filtering Clauses

LIKE '<pattern>'

Filters facts to those whose name matches the pattern. Uses SQL LIKE pattern syntax: % matches any sequence of characters, _ matches a single character. Matching is case-insensitive (the extension maps LIKE to DuckDB’s ILIKE). The pattern must be enclosed in single quotes.

IN SCHEMA <schema_name>

Filters facts to those in semantic views belonging to the specified schema.

IN DATABASE <database_name>

Filters facts to those in semantic views belonging to the specified database.

STARTS WITH '<prefix>'

Filters facts to those whose name begins with the prefix. Matching is case-sensitive. The prefix must be enclosed in single quotes.

LIMIT <rows>

Restricts the output to the first rows results. Must be a positive integer.

When LIKE and STARTS WITH are both present, a fact must satisfy both conditions (they are combined with AND).

Warning

Clause order is enforced. LIKE must come before IN, and STARTS WITH must come after IN. Placing clauses out of order produces a syntax error.

Output Columns

Returns one row per fact with 8 columns:

Column	Type	Description
database_name	VARCHAR	The DuckDB database containing the semantic view.
schema_name	VARCHAR	The DuckDB schema containing the semantic view.
semantic_view_name	VARCHAR	The semantic view this fact belongs to.
table_name	VARCHAR	The physical table name the fact is scoped to.
name	VARCHAR	The fact name as declared in the FACTS clause.
data_type	VARCHAR	The inferred data type (via typeof when the underlying table contains data). Empty string if the type has not been resolved.
synonyms	VARCHAR	JSON array of synonym strings (e.g., ["discounted_price"]). Empty string if no synonyms are set.
comment	VARCHAR	The fact comment text. Empty string if no comment is set.

Examples

List facts for a single view:

Given a semantic view orders_sv with one fact on a table that contains data:

SHOW SEMANTIC FACTS IN orders_sv;

┌───────────────┬─────────────┬──────────────────────┬────────────┬────────────┬────────────────┬──────────┬─────────┐
│ database_name │ schema_name │ semantic_view_name   │ table_name │ name       │ data_type      │ synonyms │ comment │
├───────────────┼─────────────┼──────────────────────┼────────────┼────────────┼────────────────┼──────────┼─────────┤
│ memory        │ main        │ orders_sv            │ orders     │ raw_amount │ DECIMAL(10,2)  │          │         │
└───────────────┴─────────────┴──────────────────────┴────────────┴────────────┴────────────────┴──────────┴─────────┘

The data_type column is inferred at define time using DuckDB’s typeof function on the underlying table. When the table contains data, the type is resolved from the expression (e.g. DECIMAL(10,2)). When the table is empty at define time, data_type is an empty string.

List facts across all views:

SHOW SEMANTIC FACTS;

Views with no facts are omitted.

Filter by pattern with LIKE (case-insensitive):

Find all facts whose name contains “amount”:

SHOW SEMANTIC FACTS LIKE '%amount%';

Because LIKE is case-insensitive, LIKE '%AMOUNT%' produces the same results.

Filter by schema:

SHOW SEMANTIC FACTS IN SCHEMA main;

Chained facts:

Facts can reference other facts. Consider a view with two chained facts:

CREATE SEMANTIC VIEW tpch_analysis AS
TABLES (
    li AS line_items PRIMARY KEY (id)
)
FACTS (
    li.net_price  AS li.extended_price * (1 - li.discount),
    li.tax_amount AS li.net_price * li.tax_rate
)
DIMENSIONS (
    li.status AS li.status
)
METRICS (
    li.revenue AS SUM(li.net_price)
);

SHOW SEMANTIC FACTS IN tpch_analysis;

┌───────────────┬─────────────┬──────────────────────┬────────────┬────────────┬────────────────┬──────────┬─────────┐
│ database_name │ schema_name │ semantic_view_name   │ table_name │ name       │ data_type      │ synonyms │ comment │
├───────────────┼─────────────┼──────────────────────┼────────────┼────────────┼────────────────┼──────────┼─────────┤
│ memory        │ main        │ tpch_analysis        │ line_items │ net_price  │ DECIMAL(18,4)  │          │         │
│ memory        │ main        │ tpch_analysis        │ line_items │ tax_amount │                │          │         │
└───────────────┴─────────────┴──────────────────────┴────────────┴────────────┴────────────────┴──────────┴─────────┘

net_price has an inferred data_type because its expression (li.extended_price * (1 - li.discount)) uses physical columns. tax_amount is blank because its expression references another fact (li.net_price), which typeof cannot resolve from a table scan. The extension resolves chained references at query expansion time.

Error: view does not exist:

SHOW SEMANTIC FACTS IN nonexistent_view;

Error: semantic view 'nonexistent_view' does not exist