| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: Multiple event triggers on a table - bug solved?
A copy of this was sent to Teus van Lingen <tvlingen_at_sqlla.com>
(if that email address didn't require changing)
On Mon, 28 Dec 1998 17:21:23 -0400, you wrote:
>No bug number, i'm afraid. The problem was experienced early 1996, so it would have
>been 7.1.x, wouldn't it? I have searched the online support-database dump available
>to OTN members, but the closed message that I could find was 440149: a request for
>a backport of bug# 252716: multiple triggers that lead to error ora-3113 or
>ora-1400. Of course, this dump is not complete and I do not have access to the full
>support database.
>
that particular bug lead to a ORA-1400 - mandatory, not null column is NULL. It wasn't that the 2 triggers were NOT firing (they were) it was that the constraint check was taking place during (intermixed with) the before row triggers and hence the constraint would sometimes see a NOT NULL column be null since the trigger that would supply its value would not yet have executed. It was due to improper sequencing of triggers and constraints and was fixed in 7.2.
It did not prevent the triggers from firing -- it sometimes, under some circumstances, prevented some data from being inserted into the database that would have gone in if all of the row level triggers had fired before the constraint was validated.
Thomas Kyte
tkyte_at_us.oracle.com
Oracle Service Industries
Reston, VA USA
--
http://govt.us.oracle.com/ -- downloadable utilities
Anti-Anti Spam Msg: if you want an answer emailed to you, you have to make it easy to get email to you. Any bounced email will be treated the same way i treat SPAM-- I delete it. Received on Mon Dec 28 1998 - 15:48:10 CST
 |
 |