Michael Hunger
Michael Hunger
Definitely not, caching nodes or id's is no problem. A node-proxy is just a thin wrapper around the long-id. so it's at most 16+8 bytes.
Also add a cache for certain node or relationship properties -> node/rel-id -> property value. Potentially as optimized column store where repeated values are only stored once or with fewer...
@crichey it uses it for its internal query -> query-plan cache. Just means we don't have to add an extra library dependency
@crichey any updates on your work, otherwise I'd love to look at this in the next weeks.
http://www.atoc.org/clientfiles/files/RSPDocuments/20070801.pdf
Thank you @theawesomenayak awesome work! Drop me an email and we get you a swag package :) perhaps we could also do a livestream together. Feel free to send a...
@yoheinakajima would you mind having a look at the neo4j integration? Thanks so much, Michael
Isn't that just CSV ? Perhaps just wrap it in base64 encoding?
You have to return relationships too or paths The browser sends a second query to pull relationships Currently it looks for certain common property-keys. But that could be made configurable...