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.

Sign up for GitHub

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

Jump to bottom

Throw a parsing exception when a reserved variable name is used #1489

Closed
lvca opened this issue Feb 29, 2024 Discussed in #1464 · 0 comments
Closed

Throw a parsing exception when a reserved variable name is used #1489

lvca opened this issue Feb 29, 2024 Discussed in #1464 · 0 comments
Assignees
@lvca
Labels
bug Something isn't working fixed
Milestone
24.2.1

Comments

@lvca
Copy link
Contributor

lvca commented Feb 29, 2024

It should not possible to use a reserve variable name, such as: "parent", "current", "depth", "path", "stack", "history" in FOREACH and LET statements. While current and parent are reserved in any context, stack, history, path and depth are used only in traverse statements.

The parser should throw an error if those variables are used.
@lvca lvca added the question Further information is requested label Feb 29, 2024
@lvca lvca added this to the 24.2.1 milestone Feb 29, 2024
@lvca lvca self-assigned this Feb 29, 2024
lvca added a commit that referenced this issue Feb 29, 2024
@lvca
fix: throw a parsing exception when reserved names are used for varia…
c85a47b 
…bles in sqlscripts

Fixed issue #1489
@lvca lvca added bug Something isn't working fixed and removed question Further information is requested labels Feb 29, 2024
@lvca lvca closed this as completed Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lvca lvca

Labels
bug Something isn't working fixed
Projects
None yet
Milestone
24.2.1
Development

No branches or pull requests
1 participant
@lvca