Andrew Bowman

I think the real problem here is that this will only work if the variable is the same for all rows. What if foo is based upon some differing computation...

Supporting usage of DISTINCT would also be great, otherwise we have to rely on `apoc.coll.toSet()` to get the list of distinct values, which is problematic because this would happen after...

+1 for Idea 2, I like the clarity this provides.

Regarding OPTIONAL UNWIND, I support the addition. We've had many users stumble across situations where they UNWIND an empty list and end up wiping out rows. Many still see UNWIND...

I don't think combining the two is the right answer. UNWIND isn't iteration, and it's not bounded the way FOREACH is, and I think that's okay. And whether the user...

@thobe No complaints there, that looks good to me. And that will cover many of the problem cases, since it looks like that wouldn't change cardinality. I still think there...

Since this is coming up again, such a constraint should probably allow both specified and unspecified direction for the relationship, to allow flexibility. Tangentially, a request for a degree constraint...

The article is a good one. I ran your query and actually got back a slightly different result set, so you may want to double-check your nodes and results: ```...

How many nodes are you returning from your queries? The results view is usually good for 300-500 nodes being returned or so, it's not meant to show huge numbers of...

Keep in mind this is a highly inefficient query, performing a cross product of every path matching the first match pattern with every single-relationship path in the graph `()-[]->()`. The...