Skip to content

docs: clarify CALL UNION variable scope (#3317) - #1

Merged
agcodes0315 merged 1 commit into
mainfrom
docs/3317-union-variable-scope
Oct 19, 2026
Merged

agcodes0315 merged 1 commit into
mainfrom
docs/3317-union-variable-scope

Conversation

@agcodes0315

Copy link
Copy Markdown
Owner

Summary

Clarifies imported-variable visibility across UNION and UNION ALL branches inside FalkorDB CALL {} subqueries.

Problem

The existing documentation explains importing outer-scope variables with WITH but does not explicitly describe how those imports behave across multiple UNION branches.

As reported in FalkorDB/FalkorDB#3317, a variable imported in the first branch is not automatically visible in the second branch on FalkorDB 4.20.7 and 6.0.2.

Changes

  • Added an explanation of branch-local variable visibility.
  • Included a reproducible query demonstrating the undefined-variable error.
  • Identified the affected tested versions.
  • Linked Issue #3317 for further context.

Verification

  • Reviewed the documentation rendering and example.
  • Referenced reproduction results reported in Issue #3317.
  • No independent database execution was performed for this documentation change.

Scope

Documentation-only clarification. No query engine changes.

Document the observed variable scoping behavior across UNION
and UNION ALL branches in CALL subqueries.

Include a reproducible example and link to issue #3317.
@agcodes0315
agcodes0315 merged commit bc3b3c1 into main Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant