Repository navigation
fix: execute saved queries in their namespace - #76
Merged
dmux merged 3 commits intoOct 29, 2026
Merged
Conversation
Collaborator
Author
|
All required checks have passed: lint, test, and UI. The PR is ready to merge. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Saved queries used by SQL job query and alert tasks now execute with their saved catalog and schema. SQL files keep the warehouse's current default namespace, and the task's warehouse remains the execution warehouse.
Add regression coverage for unqualified saved query SQL when the default namespace contains a conflicting table; verify both query jobs and alert evaluation read the saved namespace.
Fixes #50
Validation
ruff format --checkandruff checkon changed filespytest -q tests/test_jobs_sql_tasks.py tests/test_saved_queries.py tests/test_alerts.py(24 passed)