Is there a way to omit or skip rollback of some data changes during a transaction rollback?
Is there a way to omit or skip rollback of some data changes during a transaction rollback? Maybe some sort of "autonomous transaction"?
The issue is with error logging in transaction. For example we may have in nested calls the following structure:
TS
<some code>
<error happens>
TRO 1
<error log to database>
but if this code is in another transaction, and that rolls back we lose error data.
Is there a way to do something like
TS
<some code>
<error happens>
TRO 1
<autonomous transaction start\flag>
<error log to database>
<autonomous transaction finish\flag>
so error log will be stored anyway?
I know about journaling switch (to disable and enable journaling in process), and it also seems working when we map error data to unjournaled database, however, maybe there are other ways?