Ann W. Harrison wrote:

> outerostic wrote:
>
>> Would it be architectually correct
>> and feasable to put a trigger on connection/disconnection to a
>> database? It would make user management an almost trivial matter.
>> (ie concurrent user license management etc).
>>
>>
>
> what operations would you like to see those triggers
> perform?
>

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.


Adriano