AltimateAI / AltimateAI/vscode-dbt-power-user

Compile pointing to different Snowflake Database when table doesn't exist

Offen
#1,591 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
bug
Vorherrschende Sprache
JavaScript
Sterne
585
Forks
121
Ø Merge
5 T. 39 Min.
Gemergte PRs (30 T.)
4

Beschreibung

### Expected behavior

I would expect the DBT Power User compilation to behave the same way that I see in the DBT Cloud IDE compilation screen, even if the table that it's referring to doesn't exist.

### Actual behavior

When I compile my code in the Cloud IDE, all of the table references point to EXAMPLE_PRD_TST_DB. But when I compile it in the DBT Power User extension, if the table doesn't exist in the Database, it seems to be defaulting to the EXAMPLE_STG_DB that is set up in the Snowflake -> Connections screen for the overall project (?). Not totally sure how it's retrieving this, but somehow it's using a different DB prefix.

### Steps To Reproduce

I use the extension for work and don't want to include our real data, so let me know if the description isn't enough information and I can try and provide some examples with sensitive attributes removed.

### Log output/Screenshots

_No response_

### Operating System

Windows 11 Enterprise - 10.0.22631 Build 22631

### dbt version

dbt Cloud CLI - 0.38.22

### dbt Adapter

Not sure what this means

### dbt Power User version

0.54.3

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.