Subject | RE: [Firebird-Architect] Autonomous Transaction Routines |
---|---|
Author | Leyne, Sean |
Post date | 2007-11-01T16:19:22Z |
Adriano,
But in these cases; wouldn't the user want to know/log whether the
operation was successful (was committed or rolled back)?
Sean
> Usage:OK
>
> 1) Autonomous triggers may be used to log (in non-external tables)
> tentatives (that may have failled) to change/insert/delete records.
> > 2) ON CONNECT trigger may call an autonomous procedure to log (in
> non-external tables) rejected access
> to connect to databases.
But in these cases; wouldn't the user want to know/log whether the
operation was successful (was committed or rolled back)?
> 3) Notify events to other processes without lose the transactioncontext.
>I don't understand, please elaborate.
> A autonomous procedure may update the database and call POST_EVENT.
> Withing the COMMIT, the events will be delivered.
Sean