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
MATCH (a {code:"TestNode/N1"})-[:LINKSTO]-b WITH collect(DISTINCT b) as coll
UNWIND coll as b1
UNWIND coll as b2
MATCH b1-[:LINKSTO]->b2 RETURN DISTINCT b1.code, b2.code;
The query works as expected when testing against a 2.1.2 install.
Results are also different on console.neo4j.org: http://console.neo4j.org/r/hv9nyb That response will include N4 and N6, which aren't among the list of nodes that N1 is related to with relationship :LINKSTO, so they should not be among "b".
The text was updated successfully, but these errors were encountered:
ricardojmendez
changed the title
Query returning nodes it shouldn't on 2.2.1
Cypher query returning nodes it shouldn't on 2.2.1
May 1, 2015
Hi,
I've tried this against several 2.2.x installs, including the recent 2.2.1 docker container.
For the following Geoff data:
This query:
Should return the following pairs:
[TestNode/N2, TestNode/N3]
[TestNode/N3, TestNode/N5]
Instead it returns
[TestNode/N2, TestNode/N3]
[TestNode/N3, TestNode/N5]
[TestNode/N3, TestNode/N2]
[TestNode/N5, TestNode/N3]
The query works as expected when testing against a 2.1.2 install.
Results are also different on console.neo4j.org: http://console.neo4j.org/r/hv9nyb That response will include N4 and N6, which aren't among the list of nodes that N1 is related to with relationship :LINKSTO, so they should not be among "b".
The text was updated successfully, but these errors were encountered: