feat: Support scalar subquery in WHERE
#111
Merged
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
MazterQyou
force-pushed
the
cubesql/subquery-where-scalar
branch
from
b39fc37
to
9a51202
Compare
MazterQyou
force-pushed
the
cubesql/subquery-where-scalar
branch
from
9a51202
to
3d0c281
Compare
waralexrom
approved these changes
Feb 6, 2024
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.
This PR is a first in series on improving subquery support (in an attempt to split the large PR into smaller chunks) enabling scalar subqueries in
WHEREand laying the groundwork for supporting other types of subqueries.TODO:
SELECTandWHEREwon't executeJOINconditions