You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OPTIONAL MATCH with WHERE false returns no row when it is the first clause #2603
When a query starts with OPTIONAL MATCH and its attached WHERE predicate is
false, the query returns zero rows. I expected one row with null values for
the optional bindings.
Adding an explicit input row before OPTIONAL MATCH preserves that row and
returns null bindings, so the behavior appears specific to OPTIONAL MATCH
at the start of a query.
I've submitted a PR with regression tests documenting this OPTIONAL MATCH behavior: #2611. @jrgemignani would love your feedback when you get a chance.
Activity
Almaryj1 commentedon Nov 13, 2026
Hi @jrgemignani @YGY-001 , I'd like to work on this. I'll add a regression test to document this OPTIONAL MATCH behaviour. Will submit a PR shortly.
Almaryj1 commentedon Nov 13, 2026
I've submitted a PR with regression tests documenting this OPTIONAL MATCH behavior: #2611. @jrgemignani would love your feedback when you get a chance.