Re: [Neo4j] IntArrayIterator: Questionable Iterable implementation

2011-05-26 Thread Pierre Fouche
in that state. I'm pretty sure I've never some across anyone, before you, that have had a problem with it. Nonetheless I think it'd be nice to fix it, and at the same time take a look at all the iterables in there. 2011/5/25 Pierre Fouche pr.fou...@gmail.com Hi, This might seem a minor point

[Neo4j] IntArrayIterator: Questionable Iterable implementation

2011-05-25 Thread Pierre Fouche
Hi, This might seem a minor point but... The method Node.getRelationships() returns IterableRelationships, implemented by IntArrayIterator. It turns out that IntArrayIterator implements both Iterable and Iterator, its iterator() method returning itself. My understanding was that an Iterable was

[Neo4j] About transactions and locking

2010-08-27 Thread Pierre Fouche
If you only need to grab a write lock on a node or relationship you can invoke the removeProperty method with a property key that does not exist. Thanks for the trick, Johan. This way I don't even have to bother releasing the lock. --Pierre ___

[Neo4j] About transactions and locking

2010-08-26 Thread Pierre Fouche
Hi, I have a few questions about transactions and locking in Neo4j. When I read the 'Isolation' section of the transaction wiki page (http://wiki.neo4j.org/content/Transactions), I understand that Neo4j provides a unique isolation level equivalent to the TRANSACTION_READ_COMMITTED in the SQL92