Skip to content
New issue

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

Common table expressions cannot be used in computed columns and quantified predicates (IN / ANY / ALL) [CORE1724] #2148

Closed
firebird-automations opened this issue Feb 4, 2008 · 7 comments

Comments

@firebird-automations
Copy link
Collaborator

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Jobin Augustine (jobinau)

i think This is a must have feature. CTE should work like a table always.
Thank you.

@firebird-automations
Copy link
Collaborator Author

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)

?

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

As for me, I would just like to see CTEs syntactically and semantically consistent with other usage cases for select expressions :-)

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1 RC2 [ 10250 ]

Fix Version: 2.5 Alpha 1 [ 10224 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: Done successfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment