John Gemignani

@ajit-satav Could you please include the results of the queries along with the queries? In particular, the full output of c1, c2, and the edge. Say, these queries instead -...

@ajit-satav For a VLE MATCH, indexes will have minimal impact on performance. The reason your query is running long is due to specifying a directionless and unlimited length edge `-[*]-`...

@ajit-satav Is this still a problem or is the issue resolved?

@eyab Would this be something you could look into?

@ns-hygao Thank you for pointing out this bug, we will address it. I will point out, though, this particular command is the same as the following, which does work -...

@ns-hygao Unfortunately, the other PR doesn't quite fix your issue. I am still working on resolving it.

This issue should be fixed in PR #1426 which is now in review.

@I33Buckler Your `create_stop_times` function is **O(N^3)** and that is inside a doubly nested loop that also does **SELECT**s from tables for each level. This can lead to as much as...

@I33Buckler If there is a cypher command causing a crash, or failing, we can try to look into that but, we will need more information about what is crashing or...

@I33Buckler If you are using that function, with the **O(N^3)** runtime, or greater, I wouldn't wait as it could take a very long time. You need to find a way...