Re: [Neo] Transaction Event Listeners

2010-01-18 Thread Raul Raja Martinez
Thanks, we'll look into the transaction manager. On Jan 18, 2010 1:21 AM, "Mattias Persson" wrote: At the moment you cannot register listeners for committed nodes or stuff like that, but you could take a look at the TransactionEventManager in the "utils" component, http://components.neo4j.org/ne

Re: [Neo] Transaction Event Listeners

2010-01-18 Thread Mattias Persson
At the moment you cannot register listeners for committed nodes or stuff like that, but you could take a look at the TransactionEventManager in the "utils" component, http://components.neo4j.org/neo4j-utils/ . You can use it to register listeners for events that you send yourself. Your listeners wi

Re: [Neo] Transaction Event Listeners

2010-01-14 Thread Raul Raja Martinez
Hi Tobias, At this time we need... - Before Transaction Commit - Dirty nodes - Properties - Relationships - After Transaction Commit - Committed Nodes - Properties - Relationships I can see how other events would be useful such as property set, removed,

Re: [Neo] Transaction Event Listeners

2010-01-14 Thread Raul Raja Martinez
Hi Tobias, thanks for the info! I'm gonna consult with my team and we'll get back with some suggestions. 2010/1/14 Tobias Ivarsson : > Hi Raul! > > Yes, Neo4j has such functionality, but we have not specified the final API > for it yet. There is code implementing it from an old API that we used in

Re: [Neo] Transaction Event Listeners

2010-01-14 Thread Tobias Ivarsson
Hi Raul! Yes, Neo4j has such functionality, but we have not specified the final API for it yet. There is code implementing it from an old API that we used in house back when Neo4j was young. I don't know if all functionality of it is still hooked up though, and it is of course undocumented. If you

[Neo] Transaction Event Listeners

2010-01-13 Thread Raul Raja Martinez
Hi, Does neo4j provide some way for adding listeners to the transaction lifecycle? We would like to intercept when transacions are commited, created and rolledback to provide our own functionality for example ensure that a given node property is always set or some other properties are within a ran