Re: Question on Insert Trigger

From: Shakespeare <whatsin_at_xs4all.nl>
Date: Fri, 7 Mar 2008 20:14:45 +0100
Message-ID: <47d1942f$0$14348$e4fe514c@news.xs4all.nl>

"DA Morgan" <damorgan_at_psoug.org> schreef in bericht news:1204914891.737927_at_bubbleator.drizzle.com...
> Serge Rielau wrote:
>> zigzagdna_at_yahoo.com wrote:
>>> Thanks to all. not null in my code was just an example. My filtering
>>> logic is lot more complex and cannot implemented through a costraint.
>>> What I am asking is there a way to do filtering in the trigger if it
>>> cannot be done using EXCEPTIONS INTO statement.
>> Can you squeeze in a view? I.e. rename the table, create select-* view
>> over the renamed table using the original table name.
>> Then create an INSTEAD OF TRIGGER on the view to intercept the rows you
>> don't like. You can ignore them, save them away, or patch them up.
>>
>> Cheers
>> Serge
>
> Another person trying to put massive overhead where a simple
> constraint would suffice: Why?
> --
> Daniel A. Morgan
> Oracle Ace Director & Instructor
> University of Washington
> damorgan_at_x.washington.edu (replace x with u to respond)
> Puget Sound Oracle Users Group
> www.psoug.org

Reminds me of the old days when views were used to force contraints on tables....

Shakespeare Received on Fri Mar 07 2008 - 13:14:45 CST

Original text of this message