Hi, In beta 6 it blocks but in the trunk we have fixed this so a read never blocks waiting for some other transaction. Instead the committed or locally modified value is read and any other concurrent modifying transaction will have its own copy.
Also in the next few days we will merge in the "transaction fix" branch that ties locking to transactions instead of threads. This means you can run two transactions in the same thread using JTA suspend/resume. You can control the locking on a finer level but this is not exposed via the core API. If you need this now, take a look at org.neo4j.impl.transaction.LockManager. You can get the lock manager for a neo service via EmbeddedNeo.getConfig().getLockManager(). -Johan On Fri, Jun 6, 2008 at 12:42 AM, Andreas Ronge <[EMAIL PROTECTED]> wrote: > Hi > > I'm trying to figure out how neo handles locking. > For example what happends when one thread updates a property and > another thread tries to reads it ? > Does it block or does it read the uncommited value ? > > And how about adding a relationship or property, locks ? > > /Andreas > _______________________________________________ > Neo mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
