Adriano dos Santos Fernandes wrote:

>>
>>
> I'll talk about similar thing, ON COMMIT triggers:
>
> Sometimes, triggers in individual tables can't allow changes that in the
> end (COMMIT) maintain the database with consistent data (business rules).
>
> One could write normal triggers in the tables that populate temp-tables
> with some data (what operations user is trying to do?), and that data is
> evaluated/validated before commit.
>
>
>

Commit triggers are absolutely dandy for doing a replication push.
Netfrastructure has had them for years (Falcon is sans Java, so no
triggers).