Mats Rydberg

Hello Ken and thanks for your report. This is very odd. In our tests we are only using the Java target for testing the generated parser. It is able to...

Hello @kenwebb and thanks for reaching back. I will leave this topic here for now, but this is a useful point to pick up from when we next plan work...

`f OF expr` works for `min`, but `collect OF expr` doesn't look as nice, unfortunately.

I'd think that adding element-wise AND and OR operators for lists, with general semantics defined as ``` [true, false, true] opAnd [false, false, true] => [true AND false, false AND...

Historically, Neo4j has supported so-called 'tombstone semantics' with respect to deleted entities; the `DELETE` operation only _marks_ the entity for deletion, and materialises this only when the query ends (during...

Hi @geoHeil and thanks for reaching out to us! Indeed, you've found the right document for nested subqueries, and as you may observe it is not yet accepted. I don't...

This seems useful. We should try to align the proposed semantics with the [UNWIND CIP](https://github.com/opencypher/openCypher/pull/230), which suggests that `null` is just another value for `UNWIND`, and is treated like a...

That idea is actually more in alignment (as in: less breakage) with the current Neo4j implementation, where `null` _is_ treated the same as the empty list. It is less in...

@jmarton What do you mean with the last paragraph?

Is there a particular point in making that distinction that I'm missing? The proposed semantics of `[OPTIONAL] UNWIND` would treat `null` identical to `[]`, but different from any other list....