On Thu, 2006-10-12 at 11:47 +0200, Martijn van Oosterhout wrote:
> What may have a better chance is assigning triggers to commands (like ON
> CREATE USER) which trigger on specific situations. No-one serious
> considered implementing this though, at it's unclear what the use-case
> would be anyway...
I see.
From MHO, the use-case would come from the same need, that made me rise
the questions. Namely: need to extend 'user' definition by application
speciffic 'things'.
My particular need was to have the ability to block the account until
its password is changed. Which I believe might (at certain point) come
into the main sources. But other applicatoins may have unforseen
requirements - It would be desirable to allow for those, event to see
just what those applications actually need.
Still. It certeinly does not justyfy entering performance panelties for
every Postgres DB aplication out there.
And yet, may be there are workarounds? Like allowing application
extentions on session SET-able variables? With troggers on update?
--
-R