Recognize Snowflake CLONE as a keyword - #910
Draft
Victor-Su-Ortiz wants to merge 1 commit into
Draft
Victor-Su-Ortiz wants to merge 1 commit into
Victor-Su-Ortiz wants to merge 1 commit into
Conversation
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
1 participant
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
Fixes #678.
Register
CLONEin the Snowflake keyword table so it is not grouped as an alias of the new database name. Cover database, schema and table clones, mixed case, quoted names, statement type, formatting, and a statement without CLONE.Verification
git diff --check: passed.make test; those logs are retained locally.AI assistance
Implementation and initial tests were produced through OpenCode using
opencode/space-bunny-free(Space Bunny). Codex reviewed the diff and independently ran the checks above. This draft has not received human code review.