Feature/support multiple column check constraints#11
Merged
marcobambini merged 3 commits intomarcobambini:masterfrom Jan 19, 2026
Merged
Conversation
- Get rid of sql3column_constraint_name
- Standardize using {} for case statements in sql3parse_column_constraints()
- Standardize tabs vs spaces in modified code
- Standardize code
stephnol
changed the title
marcobambini
approved these changes
Jan 19, 2026
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
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.
Support a constraint name for every type of column constraints.
Define and use a sql3checkconstraint struct for column check constraints.
Support multiple column check constraints.
Standardize using {} for case statements in sql3parse_column_constraints().
Standardize tabs vs spaces in modified code.