Subject | Re: [Firebird-Architect] Autonomous Transaction Routines |
---|---|
Author | Adriano dos Santos Fernandes |
Post date | 2007-11-02T16:11:45Z |
Leyne, Sean escreveu:
The ones without this was rolled back.
others connections in a SP without waiting for the client to commit the
transaction that called the SP.
Adriano
> But in these cases; wouldn't the user want to know/log whether theA committed status/record could be written in the normal transaction.
> operation was successful (was committed or rolled back)?
>
The ones without this was rolled back.
>Using normal operation of POST_EVENT / COMMIT, one may notify events to
>> 3) Notify events to other processes without lose the transaction
>>
> context.
>
>> A autonomous procedure may update the database and call POST_EVENT.
>> Withing the COMMIT, the events will be delivered.
>>
>
> I don't understand, please elaborate.
others connections in a SP without waiting for the client to commit the
transaction that called the SP.
Adriano