Re: trigger question

Morning Tony,

I notice from a few of your subsequent postings that you got some replies - I didn't see them, so apologies if this is duplicating information you already have.

In your trigger error handling code, do this :

exception
 when dup_entry_exception then
  raise_application_error(-20000,
   NULL;
 when others then
   raise;

Shove the above into your exvception trigger and it will not raise an exception when it detects a duplicate and the duplicate row will not be inserted. However, if another error occurs, it will be raised. You could leave out the 'when others' clause and the same would occur - I like to be explicit.

HTH Cheers,
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