Re: trigger question
Date: 1996/03/29
Message-ID: <4jhkbe$nt4_at_inet-nntp-gw-1.us.oracle.com>#1/1
parris_at_duart.esp.bellcore.com (Parris Geiser) writes:
> Chris,
> Let me be more clear. The trigger will be sending something via an alert
> to a PRO*C program. The program will then take some action, like sending
> mail etc. So, here is the point: I don't want the program notified if the
> transaction does a rollback. Got it?
> parris
>
> Chris Kasten (kasten_at_brookings.net) wrote:
> > parris_at_duart.esp.bellcore.com (Parris Geiser) wrote:
> > > Hi,
> > > We would like to execute a trigger when a record is
> > > inserted, but only if the transaction commits.
> > > That is, if the user inserts a record and then subsequently
> > > does a rollback, we don't want the trigger to fire.
> > > Is there any way to do this?
> > > Thanks for your help.
> > > parris
> > Isn't that a non-issue? You can't commit or rollback within
> > the trigger so if the user does a rollback *everything* rolls
> > back, no?
> > hth,
>
>
Alerts are transactional. If the signaling transaction rolls back, signal() is ignored.
It is documented in Server Application Developer's Guide Appendix A
Sergiusz
"The opinions expressed here are my own, and are not necessarily that of Oracle Corporation" Received on Fri Mar 29 1996 - 00:00:00 CET