Fix issue 2106: Add parsing functionality for MySQL ALTER Table option statements #2115
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
This PR addresses the issue with #2114 to parse specific MySQL-specific features in ALTER TABLE statements, such as ENCRYPTION, AUTO_INCREMENT, and ENGINE options. Previously, these clauses were categorized as
UNSPECIFIC
.Changes
Modified the parser to correctly identify and handle the
ENCRYPTION
option in ALTER TABLE statements.Added support for parsing the
AUTO_INCREMENT
option in ALTER TABLE statements.Implemented parsing functionality for the
ENGINE
option in ALTER TABLE statements.These options are now categorized under
SET_TABLE_OPTION
instead ofUNSPECIFIC
.References
MySQL Documentation: ALTER TABLE Partition Operations