This repository was archived by the owner on Jun 8, 2026. It is now read-only.
Repository navigation
fix: classify batched DDL statements - #360
Merged
Merged
Conversation
larkee
marked this pull request as ready for review
June 18, 2021 07:34
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Currently an SQL statement such as
"CREATE TABLE t (...); INSERT INTO T (...)"would be classified as batched DDL despite not all the statements being DDL.This PR adds a classification check for each of the statements and raises an error if any of the batched statements are non-DDL.