Re: Transaction already aborted.
Not sure exactly where your errors originate from.
The 4350 comes from calling execute(Commit) when the
transaction already has been aborted.
The transaction is automatically aborted when a serious
error occurs in a call to the NDB API.
The above looks good to me, but potentially I gather an error
could occur in equal or setValue calls, but need to know more
exactly where the program fails to give more input.
Subject
Views
Written By
Posted
943
September 18, 2017 12:05AM
Re: Transaction already aborted.
452
September 19, 2017 08:09AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.