>> When you consider the flag
>> table maintenance has to go around BEGIN ... WHEN ANY ... END
>> blocks - it gets quite horrible to maintain and starts to make
>> even the most simple procedures quite ugly.

> Probably GTT ON COMMIT DELETE ROWS would be helpful there

Certainly GTT is a feature I did not consider last time, and
certainly the ON COMMIT DELETE ROWS aspect could prove very
useful...

I would need to analyse each situation to be sure it is going
to be OK to have the raised privileges flag visible outside the
scope of the specific procedure(s) that need the feature. It
is easy to imagine writing code that calls a procedure needing
raised privileges and then calling another that assumes user's
privileges... that second procedure would accidently pick up
the residual raised privileges flag, with potentially
unexpected results.

I am not saying I have any specific situations where this
happens right now... I think it is unlikely, but I would have
to study the code to make sure - and cant say I like the
potentially unpredictable nature of this option.

--
Geoff Worboys
Telesis Computing