This question is locked. New answers and comments are not allowed.
Hi forum,
I have a quick question.
When calling the "commit" method (or "rollback"), is the transaction made inactive just after the call, or may it occurs sometime that the transaction remains active (even some milliseconds).
I have a multi threaded application, and it seems that although I have put some protection on the transaction not to allow several threads accessing the database at the same time, I some times have an error when trying to open a transaction: "Transaction already active".
So do I have to wait for the transaction to be inactive after a commit or a rollback to allow another thread to open it again?
Thanks for your response,
Antoine.
I have a quick question.
When calling the "commit" method (or "rollback"), is the transaction made inactive just after the call, or may it occurs sometime that the transaction remains active (even some milliseconds).
I have a multi threaded application, and it seems that although I have put some protection on the transaction not to allow several threads accessing the database at the same time, I some times have an error when trying to open a transaction: "Transaction already active".
So do I have to wait for the transaction to be inactive after a commit or a rollback to allow another thread to open it again?
Thanks for your response,
Antoine.