Adriano dos Santos Fernandes wrote:

> Triggers fired in database events are useful for many things:
> On connect/disconnect for logging or logon control.

I thought that was what the security / authentication subsystem
was supposed to do.

> On begin transaction for implementation of a "writable transaction
> id" (incrementing a generator and storing in a context variable).

Don't we have a mechanism for creating transaction ids? Do we really
need two different ones - one of which uses a generator so it can be
bumped or reset?

> On commit triggers for business rules validations.

The standard describes that at the role of deferred constraints.


Before we get into syntax, lets look at semantics.


Regards,


Ann