We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Submitted by: @dyemanov
Votes: 1
Parser rules column_select and column_singleton should be extended to allow the WITH [RECURSIVE] clause.
Commits: 0c51514 b028c90 736feae
The text was updated successfully, but these errors were encountered:
assignee: Vlad Khorsun [ hvlad ]
Sorry, something went wrong.
Commented by: Jobin Augustine (jobinau)
i think This is a must have feature. CTE should work like a table always. Thank you.
Commented by: @hvlad
About usage of CTE in quantified predicates :
Why do you prefer
select ... from ... where ... in (with recursive ... select ... from cte)
but not
with recursive ... select ... from ... where ... in (select ...from cte)
?
Commented by: @dyemanov
As for me, I would just like to see CTEs syntactically and semantically consistent with other usage cases for select expressions :-)
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Fixed [ 1 ]
Fix Version: 2.1 RC2 [ 10250 ]
Fix Version: 2.5 Alpha 1 [ 10224 ]
status: Resolved [ 5 ] => Closed [ 6 ]
status: Closed [ 6 ] => Closed [ 6 ]
QA Status: Done successfully
hvlad
No branches or pull requests
Submitted by: @dyemanov
Votes: 1
Parser rules column_select and column_singleton should be extended to allow the WITH [RECURSIVE] clause.
Commits: 0c51514 b028c90 736feae
The text was updated successfully, but these errors were encountered: