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
If a query like this:
"""
create (m)<-[r1: HAS_CREATOR]-(p1)
create (m)<-[r1: HAS_CREATOR]-(p2)
"""
we should throw a exception: "Variable r1 already declared"
but now, we can create relationship correctly, it seems the latter r1 will cover r1 before. But if the context want use the earlier r1, the logic will not be correct.
The text was updated successfully, but these errors were encountered:
LianxinGao
changed the title
cypher need to check schema
Lynx need to check cypher schema
Jul 6, 2022
I think it is ok. Because a variable has its own scope. There are cases where users are making mistakes to reuse variable name, but there are cases where reusing variable are ok.
I think it is ok. Because a variable has its own scope. There are cases where users are making mistakes to reuse variable name, but there are cases where reusing variable are ok.
If a query like this:
"""
create (m)<-[r1: HAS_CREATOR]-(p1)
create (m)<-[r1: HAS_CREATOR]-(p2)
"""
we should throw a exception: "Variable
r1
already declared"but now, we can create relationship correctly, it seems the latter r1 will cover r1 before. But if the context want use the earlier r1, the logic will not be correct.
The text was updated successfully, but these errors were encountered: