> You could use ON TRANSACTION COMMIT trigger with, probably, help of

RDB$SET_CONTEXT\RDB$GET_CONTEXT functions. But it fire at transaction
commit time, not after.

I'm assuming the trigger fires within the context of the transaction
that is committing. Thanks for the tip, I'll be back with questions
concerning that approach.

> If you need after commit - use events.

That would be the cleanest implementation, except it would require
something outside the database. This is a data integrity issue, and I'd
like the database to keep all the relationships straight.

-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Vlad Khorsun
Sent: Friday, May 01, 2009 1:40 PM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Table transactional triggers

> Is it possible to have a trigger fire for an insert/update/delete only

> after all changes to the table have been committed?

No

> I'm not up-to-date on 2.0 - 2.5 so I may have missed it

You could use ON TRANSACTION COMMIT trigger with, probably, help of
RDB$SET_CONTEXT\RDB$GET_CONTEXT functions. But it fire at transaction
commit time, not after. If you need after commit - use events.

Regards,
Vlad

Disclaimer: This message (including attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. RxStrategies, Inc. shall not be liable for the improper or incomplete transmission of the information contained in this communication or for any delay in its receipt or damage to your system. RxStrategies, Inc. does not guarantee that the integrity of this communication has been maintained nor that this communication is free from viruses, interceptions or interference.