thanks. I am a bit reluctant to share the query itself here at this time. However, your answer actually reminded me of another
issue. Although the match with 'where: ...' works as expected, returning all data (very fast also when limit is 400+).
Applying my 'arcsinh(arg)' function to columns in the return part did not work. Hence the attempt with select, which works, but very very slow even when adding PARALLEL(which even in my 2.2.5 makes a big difference).
By the way, how can MATCH show data from two "branches" (or a fork) from a vertex with two edges?
As you say, MATCH is probably not yet fully matured, so I am looking forward to upcoming versions. Having said this, I would like to add
that in the latest releases you made fantastic progress!
Regarding the alias part in the RETURN section. From my point of view, the example I referred from you blog post is perhaps a bit
superfluous? Why return aliases when the select columns would need yet another set of aliases as well?