application.
This is the expected behavior.
Best Regards,
Thomas
-Original Message-
From: Florian Schmitz [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 14. Februar 2006 10:38
To: Anhaus, Thomas
Subject: Re: Problem creating Trigger
Hello Thomas,
see the attached trace.
Trigger-Defi
I've found an old mail saying that OLD and NEW works only in UPDTE
triggers. So, should I not use OLD in DELETE trigger too?
Thanks,
Richter
Edson Carlos Ericksson Richter escreveu:
Thank you, you is right. I forgot the brackets...
But now, if I stay with "if old.CO_SITUACAO <> 2", I get "T
I think this is true for MS SQL Server, but not for MaxDB (so you should
never use :old in FROM clause).
Someone at MaxDB team could confirm this?
Thanks,
Richter
Fabrice Bourdel escreveu:
hi,
triggers are fired when there is one line deleted... or more than
one too; And because then variab
Thank you, you is right. I forgot the brackets...
But now, if I stay with "if old.CO_SITUACAO <> 2", I get "Table name
must be in from list". If I remove the IF line, compiles ok.
Any hints?
Richter
Frank Schimmelpfennig escreveu:
Hi,
perhaps it helps to put the trigger logic between brac
Hi,
perhaps it helps to put the trigger logic between brackets... Pls. see the
code modifications below:
create trigger TRG_PARCELA_DEL for TB_PARCELA
after delete
execute (
if old.CO_SITUACAO <> 2 then
UPDATE MGR.TB_CC_ORCAMENTO
SET VL_PROVISIONADO = VL_PROVISIONADO
hi,
triggers are fired when there is one line deleted... or more than
one too; And because then variables "old.*" could represent more
than one record, the update query you written is a problem.
That's why there is an error message ;
> -Message d'origine-
> De : Edson Carlos Ericksson Ric
