Chris Leishman

Hey @AO-StreetArt: Full support, whatever that means ;-) Retrieving the routing table can already be done: it's just a cypher query to a stored proc (which is what makes it...

Hi @AO-StreetArt, Thanks for making this initial foray! I think this sounds like a good initial scope. My only comment is that I'd prefer not to expose it using a...

Hey! Before you get too far ahead, it'd be good to share your code and get some feedback. I'd hate to ask to rework a lot after you'd written a...

Here's the API I'd suggest: ``` neo4j_driver_t *driver = neo4j_driver("bolt+routing://....", config, flags); neo4j_connection_t *connection = neo4j_session(driver, NEO4J_WRITE_SESSION); neo4j_result_stream_t *results = neo4j_run(connection, "RETURN 'hello world'", neo4j_null); ``` (obviously with error handling...

@aseemk Based on the examples, I'm guessing that _it is_ only the `RETURN` values that are made available to the outer query. It's just that the language isn't very clear...

Hi @terribleplan, Thanks for the input. This is almost a duplicate of #340. Certainly there are constraints that require knowing the labels in statements that require index selection - use...

Have you considered generating the queries to contain the appropriate label then? Middleware for SQL databases also has the same challenge, as you can't parameterize table or column names. It...

I'll leave it open for now, and pass the feedback along to our team. Thanks for taking the time to provide it!

The concern with parametrized labels was that the actual label wouldn’t be available during query planning, and thus the query could not be optimised to use indexes, etc. That could...

``` MATCH (a)-[r]->(b) WHERE type(r) = {param} ... ``` That should work.