Repository navigation
fix(snowflake): compare the bare database name when dropping a catalog #6208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
DG47
wants to merge
1
commit into
SQLMesh:main
Choose a base branch
from
DG47:fix/snowflake-drop-catalog-quoted-name
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Check the database that Snowflake will drop.
If
QUOTED_IDENTIFIERS_IGNORE_CASEis true, Snowflake resolves"my-db__dev"as"MY-DB__DEV". If both databases exist and the lowercase one is marked as managed, this check passes but the drop targets the uppercase database, even if it is unmanaged. This can occur after the session parameter changes. (docs.snowflake.com)Resolve the name under the session’s identifier rules before checking its managed status. Add a test for this case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This already happens on main for names that don't need quoting:
drop_catalog("foo")checksDATABASE_NAME = 'foo'and then runsDROP DATABASE IF EXISTS "foo"(that's whattest_drop_catalogasserts), so withQUOTED_IDENTIFIERS_IGNORE_CASEon it resolves toFOOin the same way. This PR only lets names likemy-db__devpass the check, and the adapter doesn't account for that session parameter anywhere else, so I'd leave it out of scope here.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Analysis chain
Script executed:
Length of output: 6994
@DG47You’re right. The existingtest_drop_catalogonmainasserts the same check and drop statements forfoo.This PR exposes the mismatch for names that need quoting, but I agree that handling the session parameter can be a separate change. The risk remains that the check can authorize a drop of a different, unmanaged database.
Would you like me to open a follow-up issue?
You are interacting with an AI system.