Gabor Szarnyas

Test case in 81d962e.

Hello @brncsk, there are two systems here: the ingraph's incremental in-memory engine and the Cypher-to-(Postgre)SQL transpiler presented in the meetup slides. Unfortunately, neither of them received much attention during this...

We've continuously had trouble with extracting good performance from transpiler SQL queries. The reasons behind this are manyfold (Postgres' optimization fence, too many subqueries, the difficulty of cardinality estimation for...

Depends on #150.

Wow, `SET` has some depth to it. [[Grammar]](https://s3.amazonaws.com/artifacts.opencypher.org/M07/railroad/Set.html) [[Docs]](https://neo4j.com/docs/developer-manual/current/cypher/clauses/set/) ``` SET n.surname = 'Taylor' SET n.name = NULL SET at = pn // copies attribute sets SET n.surname = $surname...

The name `Set` is prone to clash with the Scala collection `Set`. I suggest we rename it to `SetOp` or something similar.

Some thoughts: - `type()` returns a single string - `labels()` returns a collection of strings - `properties()` returns a map - `keys()` returns a collection of strings Propagating these in...

Also, `m:Message`-style expressions could also be considered to be metaqueries as they are a special case of `'Message' IN labels(m)`-style expressions.

`:NodeLabel`-style expressions now work, except when there are joins (expands or plain Cartesian products), in which case the schema inferencer just crashes because it does not propagate the variable either...

The stored procedure is almost ready, but this will only be required by the Social Network Benchmark.