RE: triggers within commit cycles

[barsa@xxxxxxxxxxxxxxxxxxx]

I believe that the trigger is fired in real time, but the records affected
remain locked until the COMMIT.  Commitment control is optimized for
transactions to commit, and not normally roll back.  COMMIT is a relatively
cheap statement (from a CPU perspective), ROLLBACK is very expensive.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com






                    "Joe Pluta"
                    <joepluta@PlutaBrot       To:     <midrange-l@midrange.com>
                    hers.com>                 cc:
                    Sent by:                  Subject:     RE: triggers within 
commit cycles
                    midrange-l-admin@mi
                    drange.com


                    08/20/01 11:43 AM
                    Please respond to
                    midrange-l






I always assumed triggers are only actually fired when the transaction is
committed.  Am I wrong in this?

Joe

> >If I update a record in a file that has an update trigger, then rollback
> the
> >transaction using commitment control, does the trigger program fire
again
> >with the correct update that puts the record back like it was?

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com