WIP: Update to sqlparser to pre-release version #13546
Draft
Conversation
This file contains 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
github-actions
bot
added
sql
This was referenced Nov 24, 2024
Merged
|
I believe the SHOW COLUMNs test is failing due to this find by @goldmedal |
alamb
changed the title
alamb
force-pushed
the
alamb/sqlparser_with_span
branch
from
038047c
to
38a8e4e
Compare
alamb
changed the title
alamb
force-pushed
the
alamb/sqlparser_with_span
branch
from
38a8e4e
to
3545647
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which issue does this PR close?
Spannedto retrieve source locations on AST nodes datafusion-sqlparser-rs#1435Rationale for this change
This PR demonstrates what is needed to update DataFusion to the next version of sqlparser-rs including new span information in sqlparser-rs
What changes are included in this PR?
Pin to a pre-release version of sqlparser-rs and update DataFusion
SHOW TABLE/SHOW COLUMNSwhich is entirely unrelated to the span thing (fixed by @goldmedal in Support relation visitor to visit theOptionfield datafusion-sqlparser-rs#1556)Are these changes tested?
Yes, by existing unit tests
Are there any user-facing changes?