RE: Interesting Exploit in PL/SQL

What does this below mean? Are you trying to say "when you MUST make sure that the program NEVER stops, regardless of whatever errors I encounter" ? If so, I can't imagine why someone would want to do that.

-----Message d'origine-----

De : oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] De la part de Nuno Souto Envoyé : mercredi, 29. novembre 2006 00:26 Cc : Oracle-L Freelists
Objet : Re: Interesting Exploit in PL/SQL

4- If you don't know what error can be generated but you MUST run the code nevertheless, then you MUST use WHEN OTHERS THEN NULL. Or pay the price of a temp table to keep all possible return codes. Otherwise your code won't run. No, I will NOT recommend coding exceptions for 20000 possible error returns!

So, rather than embark in yet another crusade of calling anyone who doesn't follow the fad an incompetent by nature, can we just for once address the problem at the root?

And ask Oracle to fix it first rather than blame everyone else for it?

--

Cheers
Nuno Souto
in windy Sydney, Australia
dbvision_at_iinet.net.au
--

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

--

http://www.freelists.org/webpage/oracle-l Received on Wed Nov 29 2006 - 11:48:44 CST