John Gemignani

I have fixed that issue, it was in code that I wrote so rather easy for me to find and correct it. A patch will be coming soon to address...

> Some feedback I can give so far: > > 1. There is a typo at line 44. > 2. The `load_vertex_hashtable` and `load_edge_hashtable` functions have many common chunks. Would...

A patch for that bug has been applied to the master branch.

I will add you shortly as I need to adjust the naming and task descriptions a bit.

I will take a look. This "should" be a relatively simple fix. I know, famous last words,...

Yep, not so simple,... The issue here is that `current_setting('my.graph')` is a function call. That means it won't get evaluated until the execution phase, which is where the query is...

Updated above comment.

@JoshInnis Was this reopened by mistake? I don't see a comment explaining why it was reopened.

Since there isn't a comment explaining why this issue was reopened, and the creator of the issue didn't reopen it, I'm closing this. Btw, @Dzordzu, the issue here is that...

``` psql-11.5-5432-pgsql=# SELECT create_graph('graph_path'); NOTICE: graph "graph_path" has been created create_graph -------------- (1 row) psql-11.5-5432-pgsql=# SELECT * FROM ag_catalog.cypher('graph_path', $$ CREATE (:L {a: 1, b: 2, c: 3}), (:L {a:...