Re: Interesting Exploit in PL/SQL

Morning Stefan,

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

I agree. It *should* only be used in those cases when you don't care if an error occurs or not. I've used it myself, but documented the code with a comment to make sure anyone reading it knows *why* I used it and why I don't care. Having said that, I don't use it very often.

Having been a developer (many languages, many systems) over the years, I find the 'when others null' discussion quite interesting and very similar to 'do not ever use a GOTO in your code'. Unfortunately, there are good reasons for both - IMHO. I use GOTOs about as frequently as WHEN OTHERS THEN NULL. Regards,
Norman.

Norman Dunbar.
Contract Oracle DBA.
Rivers House, Leeds.

Internal : 7 28 2051
External : 0113 231 2051

Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.

We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.

We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.

If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk

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