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 expression context could be used with parameters [CORE2699] #3099
Comments
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 Alpha 1 [ 10331 ] |
Commented by: Sean Leyne (seanleyne) Adriano, Could you clarify are you saying that CTE should support parameters? |
Commented by: @asfernandes The test case should result in an error, but wasn't. |
Commented by: Sean Leyne (seanleyne) Adriano, Again, could you clarify, what is the error? |
Commented by: @dyemanov AFAIU, the bug is that the engine silently accepts the "parametrized" syntax (10 in parenthesis in the example above) while it should throw an error, as such a feature is not intended. |
Commented by: Sean Leyne (seanleyne) If the feature is not intended, that's fine. I should point out, however, that the readme documentation for CTEs suggests that parameters are supported:
The "CTE_A [(a1, a2, ...)]" certainly gives the impersion that parameters are supported. What else could "(a1, a2, ...)" be, but parameters? |
Commented by: @asfernandes This is not parameters. This is field names, like CREATE VIEW X (a1, a2, ...) ... What is invalid is WITH CTE_A ... SELECT * FROM CTE_A (<parameters>) |
Modified by: @asfernandesdescription: Test case: Obviously, parameters do nothing here. => Test case: Obviously, parameters usage is not correct here. |
Commented by: @pcisar Test created. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @asfernandes
Is related to QA547
Test case:
with x as (
select 1 n from rdb$database
)
select * from x(10);
Obviously, parameters usage is not correct here.
Commits: 0145996 ed0e0da
The text was updated successfully, but these errors were encountered: