Re: triggers within commit cycles

["R. Bruce Hoffman, Jr." <rbruceh@xxxxxxxxxxxxx>]

-----Original Message-----
From: Leif Svalgaard <leif@leif.org>
To: midrange-l@midrange.com <midrange-l@midrange.com>
Date: Monday, August 20, 2001 3:10 PM
Subject: Re: triggers within commit cycles


><sigh>
>A complicated screen may invoke dozens of business rules
>on several files or tables. Several screen interactions may be
>necessary to finish the BUSINESS transaction. At the very
>end the user may cancel the whole thing. All the intermediate
>steps should not be journaled or triggered because they are
>not transactions.


Ok, I think you have something very specific, some scenario, in mind that I
am not privey to, but...

I have to ask....

if the steps in between are not part of the business transaction, what are
they doing in the middle of a business transaction?

The commit cycle is defined by the business transaction and vice-versa. It
is designed and coded that way. If you are accepting a credit card, you
don't send mail to aunt Edna for her birthday in the middle of the
transaction... do you?

If you are just thinking of the auto commit functions like in ODBC or ISQL,
then no, we are talking apples and orangutans...

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - AS/400 Administrator
 -- IBM Certified Specialist - RPG IV Developer

"America is the land that fought for freedom and then
  began passing laws to get rid of it."

     - Alfred E. Neuman