The PagingIterator caches the results lazily going forward with the ability to go back through the pages. Going forward again will return cached values as far as possible and then go down to the real iterator again when the end of the cache is reached. So it will not cache the entire result up front. It will probably not impose any performance problems/differences.
2011/7/27 Jim Webber <j...@neotechnology.com> > Hi John, > > OK, gotcha. I didn't realise there's a network hop in there too. > > Go ahead on use the PagingIterator. > > Jim > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > -- Mattias Persson, [matt...@neotechnology.com] Hacker, Neo Technology www.neotechnology.com _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
