Today's Quandry...

A question… If I am writing an OScript function and my CS is using an Oracle DB backend, if I rollback a transaction that I start in Level2() (as part of DoMoreStuff) will the transaction that I start in the function Level1() also be rolled back..?

Function Level1( args ) {
     …
     DoStuff
     …
     CAPI.StartTransaction()
     …
     Level2()
     …
     DoMoreStuff
     …
     CAPI.EndTransaction()
}

Function Level2( args ) {
     …
     DoStuff
     …
     CAPI.StartTransaction()
     …
     DoMoreStuff
     …
     CAPI.EndTransaction()
}

Thanks in advance for the insight…

Jim Brezina

Lead Technical Consultant,

OpenText Optimize Service Programs

Mobile: (847) 361-4471

Find more posts tagged with

Comments

sıɹɥɔ

Hi Jim,

Content Server abstracts transaction logic, so it doesn’t matter what underlying dbms is in use: you’ll have the same behavior for all supported database systems. CAPI provides for nested transactions, and your program logic will be coordinated with it. To answer your question, in your example it doesn’t matter whether your Level2 code commits or rollsback; it’s up to the outer Level1 to determine the final outcome (assuming, of course, that Level1 isn’t also nested). If Level1 commits then whatever happened in Level2 is also committed; if Level1 rollsback then the rollback also applies to Level2.

I’ll connect with you directly to followup.

Thanks,

-chris

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Thursday, March 21, 2019 2:47 PM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: Today's Quandry...

Today's Quandry...

Posted byjimb@opentext.com (Brezina, Jim) On 03/21/2019 05:44 PM

Function Level1( args ) {
     …
     DoStuff
     …
     CAPI.StartTransaction()
     …
     Level2()
     …
     DoMoreStuff
     …
     CAPI.EndTransaction()
}

Function Level2( args ) {
     …
     DoStuff
     …
     CAPI.StartTransaction()
     …
     DoMoreStuff
     …
     CAPI.EndTransaction()
}

Thanks in advance for the insight…

Jim Brezina

Lead Technical Consultant,

OpenText Optimize Service Programs

Mobile: (847) 361-4471

Chris Meyer

Only the outer most transaction determines whether to commit all the transactions. This makes sense since applying some transactions but not others would almost certainly lead to data corruption.

However, this also means you must be careful with error handling. If an error occurs in an inner transaction then the error must be bubbled up to the outer most transaction such that it can apply a rollback. A few years ago I wrote a blog post about this topic.

Finally, get in the habit of using the prgCtx.fDbConnect.StartTrans() and prgCtx.fDBConnet.EndTrans(<commit>) functions for starting and ending transactions. They wrap CAPI.StartTransaction() and CAPI.EndTransaction(), but do some other important things.