I just committed a fix for it (rev. 3017) ... it should do the trick 2009/7/28 Mattias Persson <matt...@neotechnology.com>: > You're absolutely right... I see the problem in the iterator > implementation of that method. I or Johan will fix that soon. > > 2009/7/27 Neil Ellis <neil.el...@peepwl.com>: >> Hi guys >> >> I noticed a side-effect in the iterator for all nodes. >> >> If you do not do a hasNext() before a next() you get a no such element >> exception. So even if I have a million nodes .next() on the first node >> throws an exception, unless I do a hasNext() check first. I believe a >> hasXXX() method should be without side effect, is that fair comment? >> >> All the best >> Neil >> >> >> _______________________________________________ >> Neo mailing list >> User@lists.neo4j.org >> https://lists.neo4j.org/mailman/listinfo/user >> > > > > -- > Mattias Persson, [matt...@neotechnology.com] > Neo Technology, www.neotechnology.com >
-- Mattias Persson, [matt...@neotechnology.com] Neo Technology, www.neotechnology.com _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
