Yes, you are right.
Still, it may be interesting in some cases to be informed when rollbacks
happen.
Mattias, thanks for your help and comments!
---
balazs
On 6/27/11 4:03 PM, Mattias Persson wrote:
> Couldn't you count those in afterCommit instead? That way you would be sure
> to update your c
Couldn't you count those in afterCommit instead? That way you would be sure
to update your counter (which isn't stored in neo4j?) for stuff that's
actually committed.
2011/6/27 Balazs E. Pataki
> Hi,
>
> So, an explicit failure() in a transaction doesn't count as a
> "transaction failed for some
Hi,
So, an explicit failure() in a transaction doesn't count as a
"transaction failed for some reason" then?
I have a counter for the number of nodes created and written to DB in
each transaction in the current thread. When the transaction fails, I
would like to know about it and not count tho
Reading the javadoc:
"Invoked after the transaction has been rolled back if committing the
transaction failed for some reason."
so it wont be notified about transactions that never even start to commit.
That's why you don't get any notifications about such transactions. Is there
any specific reas
Hi,
I'm using 1.4M03 and I have class implementing TransactionEventHandler.
However it never receives an afterRollback() although I call failure()
and finish() on the transaction. Otherwise the transaction seems to be
rolled back, only my TransactionEventHandler is not informed about it.
befo
5 matches
Mail list logo
