GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||
GeezerVison is showing github.com — Fix parsing `ALTER TABLE ... ADD COLUMNS (...)` by njaremko · Pull Request #2087 · JSQLParser/JSqlParser Conversation
|
| ( | ||
| <K_COLUMN> { alterExp.hasColumn(true); } | ||
| | | ||
| <K_COLUMNS> { alterExp.hasColumns(true); } |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
It seems I auto-formatted this file. This is the only change, but I can remove the formatting bit if that matters.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
84ed566 to
9672d76
Compare
|
Thank you for your contribution, please fix formatting exception by running './gradlew :spotlessApply' to fix these violations. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
The current behaviour fails when it encounters `ADD COLUMNS` and merges everything in the `()` into one string with no whitespace. So `ALTER TABLE catalog.table.name ADD COLUMNS (apples int)` becomes `ALTER TABLE catalog.table.name ADD COLUMNS (applesint)`. This commit adds an understanding of how `ADD COLUMNS` to the grammar.
9672d76 to
bcdadc8
Compare
|
Done |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thank you for your contribution! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.