"outerostic" <outerostic@...> wrote:

> Would it be architectually correct and feasable to put
> a trigger on connection/disconnection to a database?

Yes, I think so. And this is registered in our feature request tracker. But
I'm not sure I like the term "trigger" in this context. Such an object has
enough semantical differences from a regular trigger. It doesn't have
OLD/NEW contexts, it doesn't make sense to have before connect/after
disconnect triggers, etc. For me, it's just a procedure that's automatically
executed by the engine in the autonomous transaction. I'd rather call it an
event handler, but it may cause confusion with the existing events
mechanism.


Dmitry