This is clear, but how do I solve this problem? Creating properties in a TransactionEventHandler like this seems like a fairly common use-case (especially for putting GUIDs on Nodes). I really don't want to have to do an extra GET after every CREATE.
It still seems that the code that turns the result into JSON should be run after the transaction is closed. Why would you form a result until you knew that the transaction was successfully committed? Bottom line is that this is a major breaking change for us and I hope there's some way to restore the previous behavior. -brian On Saturday, January 25, 2014 4:38:17 AM UTC-5, Andres Taylor wrote: > > > I was unclear : > > On Sat, Jan 25, 2014 at 10:21 AM, Andres Taylor < > [email protected] <javascript:>> wrote: > >> The transaction isn't closed until after the Cypher statement is closed, >> and so Cypher can't see what a transaction event handler does inside the >> transaction. >> > > "event handler does at the end of a transaction" was what I meant. > > Andrés > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
