Skip to content
Back to skills

323 Dynamic Sql 94831248

ASecurity

Some SQL patterns that work in legacy dbt may not be supported by Fusion's static analysis, such as: ```sql PIVOT(...) FOR column_name IN (ANY) ```

  • 9 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 11, 2026
code-qualitysql

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 323-dynamic_sql_94831248 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 323 Dynamic Sql 94831248?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 323 Dynamic Sql 94831248
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-323-dynamic-sql-94831248/badge)](https://www.skillsdirectory.com/skills/tools-only-323-dynamic-sql-94831248)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
# Limitations of Dynamic SQL

## PROBLEM

Some SQL patterns that work in legacy dbt may not be supported by Fusion's static analysis, such as:
```sql
PIVOT(...) FOR column_name IN (ANY)
```

## SOLUTION

The first option is always preferred and should be attempted first, if possible. 

### option 1: refactor

refactor away any instances of `PIVOT(...) FOR column_name IN (ANY)` to have hard-coded values.

### option 2: disable static analysis

For models with unsupported dynamic SQL:
1. Add `static_analysis = 'off'` to the model config:
```sql
{{
    config(
        materialized = 'table',
        meta = {
            'static_analysis': 'off'
        }
    )
}}
```

2. Or disable static analysis globally for the model in `dbt_project.yml`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.