Re: Trigger on table with many fields

"michaelg" <mikespanien_at_hotmail.com> wrote:

> I have a problem using a trigger on a table with many field (>150).
> This is the trigger :

This is a huge number of fields. Bigger than one would normally expect for a decently designed system, unless you have a very particular situation.

> The trigger works fine, but because of internal reasons in our system
> we save the trigger, when table1 is deleted and recreate it when table1
> gets created. But the table where it is saved, is quite short and it is
> not possible to change it, so the trigger body is cut offed. Do you
> have any ideas, how to optimize this trigger, to get it shorter ? I
> thought to call a function, which fills the field, but I am quite
> newbie in Oracle.

Are you performing DDL while an application is running? This is a recipe for disaster. Your system should be designed so that no DDL is performed during "normal" operation.

Paul...  

> Mike

-- 

plinehan __at__ yahoo __dot__ __com__

XP Pro, SP 2, 

Oracle, 9.2.0.1.0 (Enterprise Ed.)
Interbase 6.0.1.0;

When asking database related questions, please give other posters 
some clues, like operating system, version of db being used and DDL.
The exact text and/or number of error messages is useful (!= "it didn't work!").
Thanks.
 
Furthermore, as a courtesy to those who spend 
time analysing and attempting to help, please 
do not top post.