[branch-0.56] Fix limit in subqueries (#1899)
#1954
Closed
Conversation
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
alamb
commented
Jul 18, 2025
| @@ -729,7 +729,7 @@ pub enum Expr { | |||
| /// `[ NOT ] IN (SELECT ...)` | |||
| InSubquery { | |||
| expr: Box<Expr>, | |||
| subquery: Box<SetExpr>, | |||
| subquery: Box<Query>, | |||
There was a problem hiding this comment.
🤔 double checking, this change it is not semver-compatible as this AST structure is part of the public API
I don't think we can release this as 0.56.1, we will have to release it in a normal release instead
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.
Part of Release sqlparser 0.56.1 (backport/fix release) #1952
Backport of Fix
limitin subqueries #1899 to 0.56.0 branchNote this PR targets
branch-0.56, not main