On Thu, Oct 12, 2006 at 12:38:08PM +0200, Rafal Pietrak wrote:
> 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.
<snip>
> And yet, may be there are workarounds? Like allowing application
> extentions on session SET-able variables? With troggers on update?
One workaround is: since you can do the create user inside a function,
write functions to do what you want and then only use them to
manipulate users.
It requires a bit of discipline, but it's doable.
Have a nice day,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
