jrsperry

given that b-tree indexes are deprecated will you consider having support for TEXT indexes? Another idea related to indexes is to include them (when queried for in a where clause...

This functionality to me at least would be very helpful from a debugging standpoint, even if it's not human readable. I've had to resort turning to the logs in my...

well that is much easier. thanks!

Although it is accessible to view in the Debug logs, it’d be helpful to have the translated query exposed so you can execute and consume the results elsewhere. I have...

I would also add that a variable length relationship matching would be incredibly valuable. In my graphs currently I've had to define "variable" length relationships within my graph in a...

just figured i'd add in again how useful adding Query Hints could be to the queries, I have a graph with quite a few relationships, and when I have a...

Update, I had a property on all nodes which was always the same and was indexed, as soon as i removed that index the planner must have switched to using...

@mrksph I have been saving large graphs similar to your example with neo4j ogm. Depending on the complexity of the graph I’ve seen it perform anywhere from 4-10 faster than...

@MacondoExpress I've noticed that the queryDirection value is not used in the where clause as well. This to me is pretty misleading as the direction specified in the property is...

Sorry I don't use Github enough, and as a result this went very stale. Yes the intent was to not change default behavior, rather just add some functionality to the...