RE: Interesting Exploit in PL/SQL

It´s somewhat funny how people tend to get tangled in formal rules set by no else but themselves.  

The simple truth is that there are no universal recipes. The answer to each such best practices question is ''it depends"  

It depends if "'when others null", goto, 101 columns table, letting developer into production db are appropriate things to do or not.    

Brgds, Laimis N.  

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Stefan Knecht Sent: 30. nóvember 2006 10:18
To: Jacques.Kilchoer_at_quest.com
Cc: oracle-l
Subject: Re: Interesting Exploit in PL/SQL

There are situations where you can use when others then null; - and it even makes sense.

For example, we've had a procedure to enable / disable auditing on all objects in a database. To avoid having to filter out all possible errors due to the huge number of different objects (and especially the sys objects) we used a construct like

begin
noaudit all on x.y;
exception
when others then null;
end;

If the noaudit fails for whatever reason (we just don't care why here), we simply go on to the next object. That was perfectly fine for this case.

Stefan

Fyrirvari/Disclaimer
http://www.landsbanki.is/disclaimer

--
http://www.freelists.org/webpage/oracle-l